openspec-continue-change

To continue an OpenSpec change, the workflow queries the current artifact status, retrieves schema-specific instructions, and writes the next artifact to the specified output path. It progresses changes by creating a single artifact per invocation.

When no change name is provided, the workflow prompts you to select one and automatically recommends the most recently modified change to ensure you continue the correct ongoing OpenSpec change lifecycle.

No, the OpenSpec change workflow enforces a structured, one-artifact-at-a-time creation process to maintain dependency awareness and context constraints, ensuring each artifact is properly validated before moving forward.

The workflow reads completed dependencies before generating the next artifact, applying dependency awareness to ensure the new artifact correctly honors context constraints and references previously completed work in the change lifecycle.

The best way to track artifact status is using the continue-change command, which checks the current status of all artifacts in the OpenSpec change and applies the correct workflow to generate the subsequent artifact.

Schema-specific guidance is required because each artifact in the OpenSpec change lifecycle has a defined structure. The workflow reads completed dependencies and applies the correct schema to ensure the artifact is valid and progresses the change.