openspec-propose

To generate a change proposal in one step, provide a change name in kebab-case or describe what you want to build. The workflow creates the change and automatically generates proposal.md, design.md, and tasks.md artifacts for implementation handoff.

Scaffolding engineering artifacts is best handled by converting a rough idea into an implementation-ready change plan. This process determines artifact dependencies and generates proposal, design, and tasks documents in the correct build sequence.

Artifact dependency orchestration works by reading openspec status and per-artifact instructions via JSON, honoring apply prerequisites, and writing each artifact to its specified outputPath until all applyRequires conditions are met.

You do not need to manually create proposal, design, and tasks files for engineering handoff. Providing a change name or feature description triggers end-to-end generation of these artifacts, ending with clear status and guidance to proceed with applying the change.

Yes, you can use this CLI workflow to align on how to build a product change. It quickly communicates what to build and why, aligns on the technical approach, and delivers a task breakdown without requiring manual scaffolding.

A limitation of one-step change proposal generation is that it requires a defined change name or clear description of what to build. It operates within openspec constraints, meaning artifact generation strictly follows JSON instructions and apply prerequisites before completing.