openspec-continue-change

To advance an OpenSpec change, you call the openspec CLI to list changes, inspect the status, and write the next required artifact using the provided template and schema rules.

Spec-driven change management is a workflow where you progress proposals, specs, designs, and task artifacts one step at a time using the openspec CLI to retrieve JSON instructions and enforce dependencies.

You create the next artifact by selecting a change, retrieving its JSON status and instructions via the openspec CLI, reading completed dependency files for context, and writing a single new artifact to the output path.

No, you do not need to manually check dependencies. The workflow reads completed dependency artifacts automatically to provide context and ensure the next artifact follows the required schema rules.

Yes, you can select which change to continue. If no specific change name is provided, you will be prompted to pick from the most recently modified changes in your OpenSpec workflow.

If an OpenSpec change is already complete, the status inspection process identifies that no further artifacts are ready, preventing the creation of unnecessary files and stopping the workflow progression.