openspec-propose

To automatically generate a change proposal, you describe a feature or bug to get a single-step proposal that creates proposal.md, design.md, and tasks.md artifacts simultaneously. This scaffolds complete change artifacts in correct dependency order for immediate implementation readiness.

Dependency-aware artifact sequencing queries openspec status and instructions to resolve artifact dependencies, then writes proposal.md, design.md, and tasks.md files in the correct order. This ensures your change scaffold has proper structural relationships before implementation begins.

Yes, you need the openspec CLI to create and inspect changes, parse instruction JSON, and write artifact files under the openspec/changes/<name> directory. The CLI handles the underlying file operations required to scaffold complete change artifacts.

Yes, you can convert a brief user idea into a fully scaffolded change with all implementation artifacts in one step. The process asks interactive clarifications when input is unclear, then generates the proposal, design notes, and task breakdown automatically without manual file creation.

The best way to remove manual scaffolding overhead is using an automated one-step proposal generation process that creates proposal.md, design.md, and tasks.md files. This eliminates manual file creation and coordination when planning features or fixes by ensuring artifacts are dependency-ordered.

Change proposal generation asks interactive clarifications when your input is unclear to ensure accurate artifact creation. It also reports progress via TodoWrite during the process, guaranteeing the resulting proposal.md, design.md, and tasks.md files accurately reflect your intended feature or bug fix.