openspec-propose

To generate a software change proposal in one step, you describe your rough idea and the system scaffolds a change directory, producing proposal.md, design.md, and tasks.md sequentially for later execution.

An automated change proposal scaffold is a generated directory structure containing proposal, design, and task artifacts. You need one when turning a rough software idea into an implementation-ready plan without manually coordinating multiple steps.

Dependency-aware artifact generation reads openspec status and instructions JSON to determine build order, checks completed dependencies for context, and stops generation once apply-ready artifacts are finished.

If your change intent is unclear, the system will ask you to clarify what you want to build before continuing. Once you provide the change name and intent, it generates the complete proposal, design, and tasks artifacts.

The best way to prepare an implementation plan is to scaffold a change directory that generates proposal, design, and tasks artifacts in sequence, fulfilling readiness gating for apply execution.

No external dependencies are required to automate task planning and proposal generation. The system operates independently to scaffold your change directory and generate the required markdown artifacts.