openspec-continue-change

To continue an OpenSpec change workflow, select the stalled change and generate the next required artifact. The workflow identifies the current change state and scaffolds the subsequent proposal, specs, design, or tasks artifact to maintain momentum.

Artifact sequencing for OpenSpec changes follows a strict progression from proposal to specs, design, and tasks. The workflow enforces this ordering by integrating with the OpenSpec CLI to check status and ensure dependencies are satisfied before scaffolding the next artifact.

Generating the next OpenSpec artifact involves using CLI integration to pull existing change details and current status. The workflow prompts for change selection, checks dependency awareness, and scaffolds the subsequent artifact aligned with the configured OpenSpec workflow.

Yes, OpenSpec change management supports progressing changes across multiple sprints by enforcing artifact ordering and maintaining dependency awareness. The workflow integrates with the OpenSpec CLI to ensure proper sequencing from proposal through specs, design, and tasks.

An OpenSpec change workflow stalls when the next artifact in the sequence is not created. This interruption breaks momentum between proposal, specs, design, and tasks phases, requiring manual or guided artifact generation to resume the configured workflow.

The OpenSpec CLI is required for status checks and workflow instructions during artifact scaffolding. CLI integration ensures the new artifact aligns with the current change state and follows the configured OpenSpec workflow sequencing and dependency rules.