openspec-continue-change

Generate the next OpenSpec workflow artifact using the OpenSpec CLI.

2|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/tonysyu/gqlxp --skill openspec-continue-change-tonysyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/tonysyu/gqlxp/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/tonysyu/gqlxp --skill openspec-continue-change-tonysyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates continuing an OpenSpec change by generating the next artifact in the workflow when a user wants to progress a change.

Core Features & Use Cases

  • Guides the creation of the next artifact in an OpenSpec change, ensuring proper sequencing and context.
  • Reads current change status, prompts for change selection when multiple changes exist, and leverages the OpenSpec CLI to generate artifacts.
  • Validates artifact creation, reports progress, and unlocks subsequent steps in the workflow.

Quick Start

Tell me which OpenSpec change you want to continue, and I will generate the next artifact in the workflow.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema
How do I continue an OpenSpec change and generate the next artifact in the workflow?

To automate OpenSpec change continuation, the skill reads current status via the CLI, prompts for change selection if multiple exist, and generates the next artifact in sequence. It enforces artifact order and writes the generated output to the specified path.

What is the OpenSpec change workflow and how does artifact sequencing work?

The OpenSpec change workflow enforces strict artifact order, requiring completion of the current step before unlocking subsequent steps. This skill validates artifact creation, reports progress, and fetches instructions via the CLI to ensure proper sequencing and context.

Do I need the OpenSpec CLI installed to automate change progression?

Yes, automating OpenSpec change progression requires the OpenSpec CLI available in your environment. The skill depends on the CLI to read status with openspec status and fetch instructions with openspec instructions to generate the next artifact successfully.

How do I check my OpenSpec change status before creating the next artifact?

You can check OpenSpec change status by running openspec status via the CLI. This skill automates that process by reading the current status to determine the next artifact in the workflow, prompting for change selection if multiple active changes exist.

What happens when multiple OpenSpec changes are active and I want to progress one?

When multiple OpenSpec changes exist, the skill prompts you to select the specific change you want to continue. It then reads the status for the selected change, fetches the required instructions, and generates the next artifact while enforcing the correct workflow sequence.

Why is my OpenSpec artifact creation not progressing to the next workflow step?

OpenSpec artifact creation may not progress if the strict artifact order is not followed or the CLI is unavailable. This skill validates artifact creation, enforces sequencing, and reports progress to ensure dependencies are resolved before unlocking subsequent steps.