openspec-continue-change

Continue an OpenSpec change by checking status and creating the next ready artifact.

Updated Jul 6, 2025
One-click install
npx skills add https://github.com/wishx127/mirror-server --skill openspec-continue-change-wishx127
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/wishx127/mirror-server/tree/main/.codebuddy/skills/openspec-continue-change
Command: npx skills add https://github.com/wishx127/mirror-server --skill openspec-continue-change-wishx127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you continue an existing OpenSpec change without manually figuring out the next workflow step, so you can move from planning to artifact creation faster and with fewer mistakes.

Core Features & Use Cases

  • Change Selection: Helps identify the correct OpenSpec change when multiple candidates exist.
  • Workflow Progression: Checks current status, finds the next ready artifact, and creates it in the proper order.
  • Guided Output: Produces the next artifact only after reading required dependencies and following schema-specific instructions.
  • Use Case: A developer returns to a partially completed spec-driven change and wants the next artifact generated without guessing the workflow state.

Quick Start

Ask me to continue a specific OpenSpec change so I can inspect its status and create the next ready artifact for you.

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a partially completed spec-driven change without guessing the next workflow step?

To resume a spec-driven change, you need a tool that checks the current workflow status and identifies the next ready artifact. This skill inspects your change state and automatically generates the next required artifact in the proper dependency order.

What is the best way to continue OpenSpec change management when multiple changes exist?

Continuing OpenSpec change management with multiple active changes requires correct change selection. This skill helps identify the specific change you want to resume, checks its current status, and creates the next artifact based on schema-specific instructions.

Do I need the OpenSpec CLI installed to generate the next artifact in a workflow?

Yes, the OpenSpec CLI is required to generate the next artifact in a workflow. This skill relies on the CLI to read artifact dependencies, check workflow progression, and respect schema-specific instructions for output creation.

How does artifact creation work when resuming a spec-driven workflow?

Artifact creation in a spec-driven workflow works by reading required dependencies before producing output. This skill ensures the next ready artifact is only created after checking the current status and following the proper ordering rules.

Why does my workflow progression stall when I try to manually plan the next spec-driven artifact?

Workflow progression stalls when you manually guess the next step and skip artifact dependencies. This skill prevents errors by checking the current status and generating the next ready artifact according to schema-specific instructions.

Can I use this approach to move directly from planning to task generation in spec-driven development?

Yes, you can move from planning to task generation by letting the skill determine the correct workflow progression. It checks the current status of your change and creates the next ready artifact, ensuring you do not skip required design steps.