openspec-continue-change

To create the next artifact for an OpenSpec change, the workflow checks status, selects a target change, fetches artifact instructions, and writes the file while respecting dependencies and constraints.

Spec-driven change management handles multiple active changes by managing change selection during the workflow. It checks the status of available changes and prompts you to select a target before fetching instructions for the next artifact.

Yes, you can use OpenSpec continue-change in automation pipelines for multi-artifact coordination. It orchestrates checking status, selecting changes, and generating required artifacts in a structured, auditable way.

Yes, the OpenSpec workflow respects artifact dependencies and schema constraints. It generates the artifact file according to the schema's rules while ensuring dependencies and constraints are satisfied.

Your OpenSpec change needs structured artifact generation to ensure the change moves forward in an auditable way. This enforces schema rules, dependencies, and constraints across the multi-artifact workflow.

The best way to progress a spec-driven change across teams is using a CLI workflow that checks change status, manages selection when multiple changes exist, and writes the next required artifact file respecting constraints.