openspec-propose

Generates complete OpenSpec change proposals with specs, design, and task artifacts.

Updated Jul 1, 2025
One-click install
npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-propose-mosakuzii0216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/mosakuzii0216/mosaku-v1/tree/main/.claude/skills/openspec-propose
Command: npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-propose-mosakuzii0216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, implementation-ready plan requires writing proposals, 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 Change Creation: Creates a change directory and generates every required artifact (proposal.md, specs, design.md, tasks.md) in dependency order. - Schema-Aware Planning: Uses the configured OpenSpec workflow schema or an explicitly requested one, following each artifact's authoritative instructions and templates. - Store and Dependency Management: Supports registered OpenSpec stores via --store flags and resolves transitive artifact dependencies so nothing the apply phase needs is missing. - 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 for the feature you want to build, for example by saying "propose a change to add user authentication".

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 change name in kebab-case or describe what you want to build. The workflow runs openspec new change, then generates every required artifact—proposal, specs, design, and tasks—in dependency order using the openspec CLI.

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 explicit request that starts the apply workflow, keeping planning and coding phases isolated.

Can I use a custom workflow schema with OpenSpec?

Yes, but only when you explicitly request a schema by name. The workflow then passes --schema <schema-name> to openspec new change; otherwise it preserves the configured default schema.

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 work silently.