openspec-continue-change

To continue an OpenSpec change, the workflow reads the current change status via the OpenSpec CLI, resolves the next ready artifact, and writes it to disk using the appropriate template. This ensures progression across the workflow without losing context.

Artifact sequencing in OpenSpec change management enforces correct ordering by reading completed dependencies and applying templates. Guardrails validate dependency awareness before writing the new artifact, ensuring alignment with the current schema and rules.

Yes, you need the OpenSpec CLI to automate workflow artifact creation. The process requires the CLI to list change status, identify the next required artifact, and apply the necessary template to write the new artifact to disk.

Dependency awareness works by reading completed dependencies before generating the next artifact. This ensures the new artifact aligns with the current schema and rules, with guardrails validating that all required dependencies are met before writing to disk.

The limitation of automating OpenSpec change progression is that it enforces strict sequencing and validation guardrails. If dependencies are not ready or the schema is not met, the workflow will not write the artifact, preventing out-of-order generation.