openspec-propose

Generate complete OpenSpec change proposals with specs, design, and tasks artifacts.

1|Updated Aug 21, 2023
One-click install
npx skills add https://github.com/jmuchovej/homelab --skill openspec-propose-jmuchovej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/jmuchovej/homelab/tree/main/.agents/skills/openspec-propose
Command: npx skills add https://github.com/jmuchovej/homelab --skill openspec-propose-jmuchovej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal requires writing specs, design documents, and task lists by hand. This Skill automates that planning phase by driving the OpenSpec CLI to scaffold a change and generate every required artifact in one guided workflow. ## Core Features & Use Cases - One-step change creation: Runs openspec new change and generates proposal.md, specs, design.md, and tasks.md in dependency order. - Schema-aware artifact generation: Reads per-artifact instructions, templates, and rules from the OpenSpec CLI so output matches the configured workflow schema. - Store and context support: Resolves registered OpenSpec stores and project context from config.yaml to ground proposals in the actual codebase. - Use Case: Describe "add user authentication" and receive a complete planning package—proposal, spec deltas, design, and implementation tasks—ready for review before any code is written. ## Quick Start Ask the assistant to propose a new change named add-user-auth that adds login and session handling to the app.

Frequently Asked Questions about openspec-propose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OpenSpec change proposal?

Provide a kebab-case change name or describe what you want to build. The workflow runs openspec new change, then generates each required artifact—proposal, specs, design, and tasks—in dependency order using the CLI's instructions and templates.

What artifacts does an OpenSpec proposal include?

With the default spec-driven schema it creates proposal.md (what and why), spec deltas under specs/<capability-path>/spec.md, design.md (how), and tasks.md (implementation steps). The exact set depends on the configured schema and its dependency graph.

Does openspec-propose implement the code after planning?

No. The workflow is strictly planning-only: it creates planning artifacts and stops. Implementation requires a separate explicit request that starts the apply workflow, such as running /openspec-apply-change.

Can I use OpenSpec with a registered store instead of a local repo?

Yes. Run openspec store list --json to discover registered store ids, then every spec and change command is invoked with --store <id>. Without a store selection, commands act on the nearest local openspec/ root.

What happens if no OpenSpec root exists in my project?

The workflow runs openspec context --json first; if it reports no_openspec_root, it stops without creating files and offers openspec init. Initialization only proceeds after you explicitly request it.