openspec-continue-change

To advance an OpenSpec change, list changes with openspec list --json, check status, select a change, and generate the next artifact to progress the workflow. If artifacts are complete, you receive completion guidance.

The OpenSpec change workflow involves listing changes, checking status, fetching instructions, and generating artifacts sequentially. It uses JSON outputs from openspec list/status/instructions to determine which artifact to create next.

Yes, you need the OpenSpec CLI to continue a change. The workflow requires JSON outputs from openspec list, status, and instructions commands to determine which artifact to create and prompt for selection when needed.

To check OpenSpec changes, use the openspec status command. This provides JSON outputs that show which artifacts are complete and which need to be generated to progress the workflow further.

When all OpenSpec artifacts are complete, the workflow provides completion guidance. The process concludes by recognizing that no further artifacts need generation for the selected change.

Yes, you can automate OpenSpec change progression across multiple changes. The workflow lists available changes via JSON, checks their status, and prompts for selection to generate the next artifact for the chosen change.