openspec-propose

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

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-propose-joeshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/JoeShi/coding-agent-usage-montior/tree/main/.kimi-code/skills/openspec-propose
Command: npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-propose-joeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable change proposal requires writing multiple planning documents by hand. This Skill automates the entire OpenSpec proposal workflow, producing proposal, spec deltas, design, and task artifacts in one guided pass. ## Core Features & Use Cases - One-step artifact generation: Creates proposal.md, spec deltas, design.md, and tasks.md in dependency order using the openspec CLI. - Schema and store awareness: Supports custom workflow schemas and registered OpenSpec stores via --schema and --store flags. - Planning-only guardrails: Strictly limits the session to planning artifacts and never edits project code or starts implementation. - Use Case: Describe "add OAuth login support" and receive a complete, validated change folder with specs and an implementation task list ready for review. ## Quick Start Ask the assistant to propose a new change named add-user-auth that adds OAuth login, and it will scaffold and fill all OpenSpec planning artifacts.

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 from a feature idea?

Describe what you want to build or provide a kebab-case change name. The workflow runs openspec new change, then generates proposal, specs, design, and tasks artifacts in dependency order using openspec status and instructions.

What artifacts does an OpenSpec proposal include?

With the default spec-driven schema it creates proposal.md, spec deltas under specs/<capability-path>/spec.md, design.md, and tasks.md. The exact set is determined by the schema and the transitive dependencies of the apply phase.

Does openspec-propose implement the change after planning?

No. The workflow is strictly planning-only and never edits project code. After artifacts are presented, you must explicitly start the apply workflow, for example with openspec-apply-change, in a new request.

Can I use a custom schema or a registered OpenSpec store?

Yes. Pass a schema name explicitly to use --schema, or name a registered store so commands run with --store <id>. Without a store, commands act on the nearest local openspec/ root.

What happens if a change with the same name already exists?

The workflow asks whether you want to continue the existing change or create a new one, rather than overwriting or duplicating artifacts silently.