openspec-continue-change

You can continue an OpenSpec change by using the openspec-continue-change skill to automate generating the next artifact. It reads completed artifacts for context, checks status via the OpenSpec CLI, and writes the new artifact to the designated output path.

If a change name is not provided when continuing an OpenSpec workflow, the system will prompt you to choose from recent changes. After selection, it proceeds automatically to create the next artifact for the chosen change.

Spec-driven change management determines artifact sequencing by relying on the OpenSpec CLI to provide status checks and dependency instructions. This ensures the correct workflow order before writing the new artifact.

Yes, you can automate artifact creation across iterations in an OpenSpec workflow. The skill automates continuing a change by generating the next output, keeping the workflow moving without manual context switching.

Yes, you need the OpenSpec CLI installed to advance a change. The skill relies on the CLI to check status, retrieve instructions, read completed artifacts, and write the new artifact to the output path.

The best way to avoid manual context switching is to use an automated workflow skill that reads prior artifacts and generates the next one. This keeps OpenSpec changes moving continuously without manual intervention.