openspec-continue-change

Generate the next OpenSpec change artifact from current status and dependencies.

11|3|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/DarkHighness/coi-public --skill openspec-continue-change-darkhighness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/DarkHighness/coi-public/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/DarkHighness/coi-public --skill openspec-continue-change-darkhighness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Progressing OpenSpec changes can be manual and error-prone; this skill automates the creation of the next artifact to maintain momentum and ensure proper sequencing.

Core Features & Use Cases

  • Orchestrates the OpenSpec workflow by reading change status and selecting the next artifact to create.
  • Executes and coordinates the OpenSpec CLI to safely progress changes, honoring dependencies.
  • Adapts to various schemas via the instruction field and writes artifacts to the specified output path.

Quick Start

Continue the OpenSpec change to generate the next artifact and advance 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 automate OpenSpec change progression to generate the next artifact?

Automate OpenSpec change progression by running the skill to check change status and automatically generate the next artifact in the approved sequence. It reads completed artifact dependencies to inform content and writes the new artifact directly to the designated output path.

How does OpenSpec determine the next artifact ready for creation in a workflow?

OpenSpec determines the next artifact by running openspec status to check the current change progress. It selects the first artifact that is ready, reads dependencies from completed artifacts, and generates content based on provided context and schema instructions.

Do I need the OpenSpec CLI installed to automate artifact creation?

Yes, the OpenSpec CLI is required to automate artifact creation. The skill executes and coordinates OpenSpec CLI commands to safely progress changes, read status, and write artifacts to the specified output path while honoring dependencies.

What is the best way to manage artifact dependencies in an OpenSpec workflow?

Manage artifact dependencies by using an automation skill that reads completed artifacts to inform the content of the next one. It uses provided context and rules strictly as constraints without copying them into the new artifact, ensuring proper sequencing.

Can I adapt OpenSpec artifact generation to different schemas?

Yes, you can adapt artifact generation to different schemas using the instruction field. The skill reads schema instructions from the response and generates the artifact accordingly, writing it to the designated output path while respecting provided context and rules.

Why does my OpenSpec change workflow fail to progress to the next artifact?

OpenSpec change workflows may fail if required dependencies from previous artifacts are incomplete. The skill relies on checking openspec status to select the first ready artifact, so ensuring all prior artifacts are completed and valid is essential for progression.