openspec-propose

To generate a change proposal, you provide a feature idea to create the proposal, design, and task artifacts sequentially. This dependency-aware workflow validates readiness before moving forward, producing an implementation-ready change package.

The OpenSpec change proposal workflow is a process that transforms a scoped fix into structured proposal, design, and task artifacts. It follows a sequential artifact generation order with dependency-aware validation to prepare work for implementation handoff.

Yes, you need the openspec CLI installed to create change proposals and task artifacts. The CLI is required to execute the sequential, dependency-aware generation workflow and validate the output artifacts before implementation.

Yes, you can use automated proposal generation for rapid feature planning instead of drafting specs manually. It turns a vague engineering idea into an organized change plan with proposal, design, and task files generated together in one pass.

The best way to structure implementation handoff packages is to generate a complete change proposal with proposal, design, and task artifacts together. This structured change package can then be applied directly using the OpenSpec workflow.

Sequential artifact generation matters because it enforces a dependency-aware workflow that checks readiness before moving forward. This ensures the proposal, design, and task files are created in the correct order with proper validation.