openspec-propose

OpenSpec scaffolding generates a complete change proposal package by creating proposal, design, and task artifacts in one step. You provide a kebab-case change name or natural-language description to seed the proposal files.

OpenSpec artifact generation automates the creation of change, design, and task documents for software teams. You need it when starting a new feature or fix to accelerate the planning phase with ready-to-implement files.

Yes, you can use a natural-language description to seed an OpenSpec proposal. The scaffolding process accepts either a kebab-case change name or a descriptive prompt to derive artifact IDs and generate the proposal package.

OpenSpec proposal generation enforces artifact dependencies and applies ready-to-implement checks. This sequencing ensures coherent generation of proposal, design, and task files according to the instruction schema.

Automating design doc creation is best handled by scaffolding all OpenSpec artifacts at once. This approach derives artifact IDs from the change name and produces proposal, design, and task files simultaneously.

One-step OpenSpec proposal scaffolding requires a kebab-case change name or description to derive artifact IDs. It respects dependency sequencing but produces files that still require team review before implementation begins.