openspec-continue-change

To continue an OpenSpec change, you select an existing change, validate its status, and generate the next artifact file in the approved sequence using OpenSpec CLI guidance. This automates the workflow progression and reduces manual context switching.

The OpenSpec change workflow enforces a strict sequence for creating artifacts, ensuring dependencies are met before progression. It validates the current change status and generates the subsequent artifact file, maintaining correct order and dependency context throughout the process.

Yes, you need the OpenSpec CLI installed to automate continuing a change. The Skill requires the CLI to read dependency context, validate status, and write the next artifact file in the approved sequence.

Yes, you can progress a change from one stage, such as a proposal, to the next by generating the appropriate artifact file. The Skill guides you through selecting the change, checking status, and writing the subsequent artifact automatically.

The Skill enforces the correct sequence and dependencies for artifact creation. If you attempt to generate an artifact out of order, the status validation step will prevent progression until the prerequisite artifacts are completed.