openspec-propose

To generate a change proposal, you describe the feature you want to build and run the CLI. This automates artifact generation by producing proposal.md, design.md, and tasks.md files to ensure end-to-end consistency across design, specs, and implementation tasks.

The best way to create implementation-ready plans is automating proposal creation from a high-level request. This process quickly converts ideas into structured plans with scope, design rationale, and a task list ready for engineering delivery.

Yes, the OpenSpec CLI workflow requires proposal, design, and tasks artifacts. This generation process produces these specific files and provides guidance to wire them into a ready-to-apply workflow for your feature changes.

Yes, you can convert feature ideas into design specs and task lists in one step. The automation generates all required artifacts including design rationale and implementation tasks directly from your single high-level request.

An OpenSpec proposal for change management includes proposal.md, design.md, and tasks.md artifacts. These files provide complete scope definition, design rationale, and a structured task list to guide end-to-end implementation and delivery.