openspec-propose

To generate a complete feature proposal in one step, provide a change name in kebab-case. The automation creates proposal.md, design.md, and tasks.md simultaneously, delivering rationale, design specifications, and implementation steps ready for stakeholder alignment.

Automating artifact creation for a new software change requires a single kebab-case input name. The system then generates a structured proposal, technical design document, and an actionable task list, ensuring product and engineering teams have aligned, ready-for-implementation outputs instantly.

You do not need to manually write separate proposal, design, and tasks markdown files. Providing a change name triggers automated content generation guided by a template, producing all required artifacts with proper dependencies in a single step.

You can align stakeholders quickly with a one-step proposal by providing a kebab-case change name. The generated artifacts include the what, why, and how of the feature, plus implementation tasks, enabling immediate review and fast team alignment.

The change name must be provided in kebab-case format to successfully generate proposal, design, and task artifacts. This specific input format ensures the automated template correctly structures the generated proposal.md, design.md, and tasks.md files.

You need an automated proposal generation tool when scoping a new feature requires quick alignment across product and engineering teams. It eliminates manual planning overhead by instantly delivering a complete proposal with rationale, design, and an implementation task list.