openspec-propose

You can generate change proposals automatically from a simple feature description, eliminating manual drafting of scope, design, and task documentation to produce implementation-ready artifacts in minutes.

Structured change proposals are needed when scoping new features, bug fixes, or process improvements where implementation-ready documentation, including design and task breakdowns, is required before development work begins.

Scaffolding change directories and resolving artifact dependencies is automated by integrating with the openspec CLI, which builds proposal, design, and task documents in the correct dependency-aware order.

Yes, openspec-propose generates complete change proposal artifacts, including design docs and step-by-step task breakdowns, for scoping bug fixes and process improvements as well as new features.

Automating implementation planning is best handled by generating compliant proposal, design, and task documents following predefined schemas from a short description of the desired change.

No, it eliminates manual drafting by automatically creating all required change proposal artifacts in one step, reading prior completed work for context to ensure consistency across documents.