openspec-continue-change

To continue an OpenSpec change workflow, the Skill lists active changes, checks their status, and generates the next required artifact in the sequence. It guides you through the proposal, specs, design, and tasks steps automatically.

The OpenSpec artifact order follows the sequence of proposal, then specs, then design, and finally tasks. The workflow enforces this step order, validates dependencies, and only produces one artifact per activation to ensure correct progression.

You cannot skip artifacts when creating OpenSpec changes. The workflow enforces strict step order and validates dependencies, prompting for missing input when context is ambiguous to keep you aligned with the active schema.

Yes, you need the openspec CLI to guide artifact creation. The Skill operates across the openspec CLI to list changes, check status, and generate the next artifact based on the active schema during the change workflow.

Your OpenSpec change workflow stops progressing when a required artifact is missing or context is ambiguous. The Skill addresses this by reading completed artifacts, prompting for missing input, and generating the next artifact to maintain forward momentum.