openspec-propose

To generate a complete change proposal, you provide a clear feature request or bug fix description. The system then scaffolds all related artifacts, automatically outputting proposal.md, design.md, and tasks.md for review and implementation.

The best way to create proposal and design artifacts is using a single-step workflow that processes your feature description into a templated, dependency-aware artifact set. This reduces planning overhead and prevents miscommunication.

Yes, you can scaffold implementation tasks automatically from a bug fix description. The workflow processes your input and generates a tasks.md file that provides step-by-step guidance to move from proposal to actionable implementation.

No, you do not need any dependencies to run the openspec proposal workflow. It operates independently to generate the full proposal, design, and tasks artifacts based solely on your provided feature or bug fix input.

Your design document is generated alongside the proposal to ensure technical alignment and reduce miscommunication. Delivering a dependency-aware artifact set in one step provides a clear, guided path from planning to implementation.

You should use a single-step proposal generator when you have a clear feature request or bug fix and need to reduce planning overhead. It delivers templated, dependency-aware artifacts that move you directly to implementation.