openspec-propose

To generate a software change proposal in one step, use an automated workflow that scaffolds a directory and produces proposal.md, design.md, and tasks.md artifacts sequentially. This ensures all change documents are created in dependency order for immediate implementation.

Turning a vague request into a structured specification involves an interactive flow that derives a kebab-case name from your description, then auto-generates matching proposal, design, and task files within a dedicated openspec directory.

Scaffolding an openspec change directory requires running an automated proposal workflow that creates a folder with a .openspec.yaml file and generates the necessary markdown artifacts, preparing the entire change for the apply phase.

You do not need to manually create proposal, design, and tasks files separately. An automated artifact-generation workflow coordinates their creation in a single step, ensuring proper dependency order and formatting before implementation.

The best way to automate design document and task generation is using a single-step proposal workflow that takes a feature description, derives a kebab-case identifier, and scaffolds all required markdown artifacts in dependency order.