openspec-continue-change

To continue an OpenSpec change, this workflow validates the current progress via status checks, reads completed dependency artifacts for context, and generates the next artifact in the enforced creation order using an instruction template.

Artifact generation determines the output path by reading the location specified within the instruction template, ensuring the new artifact file is written correctly to continue the OpenSpec change workflow.

The workflow validates current progress with status checks and enforces artifact creation in the correct order, preventing progression if required dependency artifacts are not yet completed.

Yes, CLI automation generates the next OpenSpec artifact by reading completed dependency artifacts for context while explicitly avoiding copying sensitive constraints into the newly created file.

The best way to orchestrate next-step artifact creation is to run status checks, read available changes and instructions, and generate the next artifact using a template based on provided instructions.

You need to validate OpenSpec status before generating an artifact to determine the next required step, ensuring the workflow moves forward by only creating artifacts in the correct sequence.