openspec-propose

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

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill openspec-propose-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/spec-driven-development/skills/openspec-propose
Command: npx skills add https://github.com/firstsun-dev/skills --skill openspec-propose-firstsun-dev

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 entire planning phase through the OpenSpec CLI, producing all required artifacts in one guided workflow. ## Core Features & Use Cases - One-step proposal generation: Creates the change directory and generates proposal.md, spec deltas, design.md, and tasks.md in dependency order. - Schema-aware artifact building: Reads the configured OpenSpec workflow schema, resolves artifact dependencies transitively, and follows per-artifact instructions and templates. - Store and context support: Works with registered OpenSpec stores via --store flags and applies project context from openspec/config.yaml as planning constraints. - Use Case: Describe "add user authentication" and receive a complete, validated change folder with specs, design, and implementation tasks ready for review before any code is written. ## Quick Start Ask the agent to propose a new change, for example: "Create an OpenSpec proposal for adding OAuth login 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?▼

Describe what you want to build or provide a kebab-case change name. The skill runs openspec new change, then generates every required artifact (proposal, specs, design, tasks) in dependency order using openspec status and instructions commands.

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 workflow schema.

Does openspec-propose implement the code after planning?▼

No. The workflow creates planning artifacts only and explicitly stops afterward. Implementation requires a separate user 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 the skill appends --store <id> to commands that read or write specs and changes. Without a store, commands act on the nearest local openspec/ root.

What happens if no OpenSpec root exists in my project?▼

The skill stops without creating files and offers openspec init. It waits for you to request initialization explicitly, then reruns the context check before continuing with the proposal.