openspec-propose

An implementation-ready change proposal is generated by converting a plain-language feature description into structured planning artifacts, producing a complete package that explains what will change and why it matters for immediate execution.

Planning design and engineering tasks for a new software change involves generating linked design and task artifacts simultaneously, ensuring all necessary implementation steps are captured in the correct dependency order from the start.

OpenSpec proposal generation works by taking a user-described feature or fix and automatically assembling the required product, design, and engineering artifacts together into a structured, apply-ready change package.

Yes, you need the OpenSpec CLI to generate proposal and task artifacts, as it provides the necessary support to create, inspect, and populate change artifacts in the correct dependency order.

Yes, you can generate a complete change package in one step by asking the system to propose a new change from your feature idea, which creates the proposal, design, and task artifacts simultaneously.

Automated change proposal generation relies on the accuracy of your plain-language feature description and the OpenSpec CLI's ability to populate artifacts, meaning highly ambiguous requirements may still need manual refinement before reaching apply-ready status.