openspec-continue-change

To continue an OpenSpec change, the workflow reads completed dependency artifacts, enforces the correct artifact order, creates a single new artifact following schema rules, and reports the generated file path alongside progress.

OpenSpec artifact creation checks the current change status and reads completed dependency artifacts to provide context, enforcing proper sequencing so that only the correct next artifact in the workflow is generated.

Yes, automating OpenSpec artifact creation prompts you interactively to select the target change name when multiple changes exist, ensuring the workflow progresses correctly for the chosen change.

The best way to enforce OpenSpec artifact sequencing is to use a status-driven automation tool that checks the current workflow state, validates dependency completion, and generates exactly one artifact per invocation following the schema.

OpenSpec artifact generation creates a single artifact per invocation by design, enforcing workflow order and dependency awareness; you must invoke the continuation process again to generate the next artifact in the sequence.