openspec-continue-change

To automate OpenSpec artifact generation, use the CLI to list changes and run the continuation command for a specific change. This reads dependency artifacts and writes the next pending proposal, spec, design, or task file automatically.

The OpenSpec continue-change process queries the workflow status, resolves the next pending artifact, reads dependency artifacts, and creates the appropriate file. It enforces schema-specific guidance from the instruction output to maintain alignment.

To push forward an OpenSpec change, run the CLI to list changes, select the target change, and execute the continue-change command with the change name. This generates the next task or design file while maintaining schema constraints.

Yes, the OpenSpec continuation workflow enforces schema-specific guidance derived from the instruction output. It reads dependency artifacts and writes the new artifact to the specified output path, ensuring the generated file aligns with schema constraints.

To continue an OpenSpec workflow, first run `openspec list --json` to list changes and pick one. Then run `openspec continue-change --change "<name>"` to generate instructions and create the next artifact file.

Reading dependency artifacts is required before creating the next file because the OpenSpec continuation process uses them to resolve the next pending artifact and enforce schema-specific guidance, ensuring the new artifact maintains proper workflow alignment.