openspec-propose

To generate implementation tasks and design docs, you can scaffold a change directory and produce proposal, design, and task artifacts in dependency order. This creates a complete set of implementation-ready documentation from a single change description.

Automating scaffolding for developer tooling involves using a CLI to create a change directory, compute artifact build order, and fetch artifact-specific instructions. This automatically structures your proposal, design, and task files consistently.

Yes, you can use openspec to turn an idea into an implementation-ready plan without manual orchestration. It builds required artifacts in dependency order until the proposal is apply-ready, stopping automatically once all outputs are written.

When artifact context is unclear during generation, the workflow uses interactive clarification by asking follow-up questions. After you provide answers, it resumes the generation process to maintain momentum and ensure accurate spec and design outputs.

Workflow automation for change proposals works for product, engineering, and process changes. It is applicable to any scenario where a complete set of implementation-ready documentation artifacts is needed to propose a structured change.