openspec-continue-change

To continue an OpenSpec change, the Skill identifies the next required artifact in the workflow sequence and guides you to create it. It checks the current status and enforces dependency rules so you resume proposals, specs, or tasks without skipping steps.

The spec-driven change management workflow enforces a specific artifact sequence: proposal, spec, design document, and task list. The Skill applies dependency checks to ensure you only create the next allowed artifact in this strict order, preventing workflow gaps.

Yes, you need the openspec CLI installed to manage artifact sequencing. The Skill requires the CLI to check change status, read workflow instructions, and enforce the one-artifact-per-invocation rule for your spec-driven development tasks.

No, you cannot create multiple artifacts at once. The Skill enforces a one-artifact-per-invocation completion rule, ensuring you advance your spec-driven change management workflow by creating only the next required document sequentially.

Your OpenSpec proposal may not advance to the spec phase due to failed dependency checks or incomplete workflow sequencing. The Skill prevents skipping steps by verifying artifact status and enforcing the correct order before allowing the next creation.

The best way to resume an in-progress OpenSpec change is to ask the Skill to identify the change by name. It reads your current status, determines the exact next required artifact, and guides you through creating it in the correct workflow order.