openspec-continue-change

To continue an OpenSpec change, the workflow inspects the current change status, identifies unblocked dependencies, and generates exactly one next artifact in sequence to maintain ordered progression.

Spec-driven change management is a workflow process that uses structured artifacts to track and guide implementation efforts. You need it when resuming specification work and requiring a guided progression from the current state to the next output file.

Creating the next artifact requires status inspection and dependency-aware progression. The workflow checks completion state and applies schema-specific instructions to produce the correct next output file without losing context.

No, the workflow creates exactly one next artifact at a time. It checks completion state, unblocked artifacts, and workflow progress before taking action to keep the change management workflow ordered and complete.

The OpenSpec continue-change workflow operates without external dependencies. It relies on status inspection and schema-specific instructions to guide the creation of the next required artifact in the sequence.

An OpenSpec workflow may stall if dependencies are unmet or the current change status is incomplete. The workflow requires status-aware progression checks before creating the next artifact to ensure ordered completion.