openspec-continue-change

Create the next OpenSpec artifact file from schema instructions and dependencies.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-continue-change-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Catsofsuffering/CCGS/tree/main/.agents/skills/openspec-continue-change
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-continue-change-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue a change by creating the next artifact and guiding the OpenSpec workflow forward.

Core Features & Use Cases

  • Prompts for a change name if not provided and lists recent OpenSpec changes to choose from.
  • Checks current status and instructions to determine the next artifact to create.
  • Creates the next artifact file based on the schema instructions and any completed dependencies.
  • Provides progress updates and guidance on unlocking subsequent steps to keep the OpenSpec workflow moving.

Quick Start

Continue a change by creating the next artifact and advancing the OpenSpec 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 create the next artifact?

To continue an OpenSpec change, the Skill checks the current workflow status, identifies the next required artifact, and generates the file based on schema instructions. It prompts for a change name if one is not provided.

What happens if I start an OpenSpec workflow without specifying a change name?

If a change name is not specified, the workflow automation prompts you to select one. It lists recent OpenSpec changes to ensure you are advancing the correct artifact progression.

How does the OpenSpec change management process determine which artifact to generate next?

The OpenSpec process determines the next artifact by reading the current change status and its dependencies. It then follows schema instructions to generate the appropriate file to unlock subsequent workflow steps.

Can I automate the progression of multiple artifacts in an OpenSpec change workflow?

This Skill automates the progression of an OpenSpec change by guiding artifact creation step-by-step. It provides progress updates and guidance on unlocking subsequent steps to keep the workflow moving forward.

What are the limitations of automating OpenSpec artifact generation?

Artifact generation relies on completed dependencies and current status checks. If dependencies are incomplete or the schema instructions are ambiguous, the workflow cannot automatically advance to the next artifact file.