openspec-propose

Generating change proposal artifacts for spec-driven development involves providing a feature description to automatically produce schema-compliant proposal.md, design.md, and tasks.md files.

The best way to automate feature planning document creation is using a CLI-driven workflow that scaffolds structured design and task artifacts from a single requirement description, eliminating manual setup errors.

Dependency-aware generation for proposal creation works by tracking artifact dependencies and automatically sequencing the generation of proposal, design, and task documents in the correct order using the openspec CLI.

You can create implementation task lists from a simple feature description because the workflow automatically translates your requirement into a structured tasks.md file ready for development tracking.

You need the openspec CLI to produce schema-compliant proposal documents because the automation relies on it to enforce project-specific constraints and generate artifacts in the correct format.

Automated proposal generation for bug fixes should not be used when your project lacks specification-driven workflows or when the required change falls outside the standard proposal, design, and task artifact structure.