openspec-continue-change

You can continue an OpenSpec change by automating status identification, fetching instructions for the next required artifact, applying the template, and generating the artifact file at the specified path.

An OpenSpec artifact is a staged file within a change-management workflow. You need to create one when progressing through ongoing OpenSpec changes that span multiple dependent artifacts and require structured file generation.

Automating OpenSpec workflow progression requires CLI-driven guidance to validate current status, select the next artifact based on dependency awareness, and apply the required template to generate the file automatically.

Yes, the OpenSpec change workflow supports dependency awareness through guarded execution, ensuring the next artifact is only generated when prior work dependencies within the ongoing workflow are satisfied.

The best way to manage multi-artifact changes in OpenSpec is to automate continuation, letting the system validate current status, fetch instructions for the next artifact, and apply the required template to generate the file.

OpenSpec artifact generation may halt during an ongoing change if guarded execution detects unmet dependencies from prior work, or if the CLI-driven guidance cannot identify the current status to fetch the next artifact instructions.