openspec-propose

Auto-generate proposal, design, and tasks documents by describing your feature change in a single input. The workflow outputs proposal.md, design.md, and tasks.md simultaneously, accelerating rapid project scoping from idea to implementation.

Automate change-management artifact generation by consolidating planning into a single workflow. Inputting your change description triggers the automatic creation of proposal, design, and tasks markdown files, reducing back-and-forth and accelerating onboarding.

Yes, you need YAML frontmatter to generate planning artifacts. The structured artifact generation process enforces a YAML frontmatter requirement containing the name and description fields before outputting your proposal, design, and tasks documents.

Yes, you can include optional components like scripts, references, and assets when auto-generating design documents. The structured artifact generation process supports these optional additions alongside the required proposal, design, and tasks files.

A single workflow generates all required planning artifacts by taking your idea input and automatically producing proposal.md, design.md, and tasks.md. This consolidated process applies to product development and change-management workflows where rapid scoping is needed.

A limitation of automated proposal generation is that it enforces a strict YAML frontmatter requirement with name and description fields. While it supports optional components like scripts and references, complex change-management workflows may require manual review of the generated artifacts.