openspec-propose

Software change proposal generation converts a rough change request into an implementation-ready package by creating proposal, design, and tasks artifacts in a single guided flow. It queries openspec status to orchestrate and order the required artifacts until the package is apply-ready.

Planning software implementation tasks from partial requirements involves orchestrating artifact generation to produce an ordered set of specs and work items. The system asks light clarification questions when intent is unclear, then generates the necessary proposal, design, and tasks files.

You do not need to manually order spec artifacts when preparing a change package. The generation process applies dependency ordering by querying openspec CLI status and per-artifact instructions, automatically writing outputs to the correct paths until the package is apply-ready.

To create proposal, design, and tasks files for a new software feature in one step, describe what you want to build and ask the system to propose the change. It generates the three markdown artifacts and instructs you to run the apply command to begin implementation.

If your change request lacks enough detail for spec generation, the system asks follow-up questions to clarify your intent and change context. Once clarified, it continues the guided flow to produce the proposal, design, and tasks artifacts.

Yes, you can use openspec-propose for fast planning from an idea or partial requirements to an ordered set of specs and work items. It is designed for scenarios where you need to quickly turn a rough concept into an implementation-ready change package.