openspec-propose

To generate a change proposal, you describe the change you want and the system derives a kebab-case name to scaffold proposal.md, design.md, and tasks.md in openspec/changes/<name>/ simultaneously. This eliminates scattered planning and manual artifact creation by producing all required documents in a single interactive workflow.

The best way to align a product development team is generating a complete change proposal with design, specs, and tasks in one step. This creates a shared set of artifacts in dependency order, ensuring everyone references the same proposal.md, design.md, and tasks.md before implementation begins.

You scaffold an openspec change directory by providing a description of your intended change. The system automatically derives a kebab-case change name and creates the openspec/changes/<name>/ directory populated with proposal.md, design.md, and tasks.md through an interactive workflow.

No, you do not need to manually name change proposals because the system uses input-driven naming. It automatically derives a consistent kebab-case change name directly from your descriptive input, ensuring standardized referencing across the generated artifacts.

To finalize implementation after generating a complete change proposal, you use the /opsx-apply workflow. This workflow takes the prepared proposal.md, design.md, and tasks.md artifacts and transitions them into the actual implementation phase.