openspec-continue-change

Generate the next OpenSpec change artifact using the openspec CLI.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-continue-change-guillaumejay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-continue-change-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by automatically creating the next artifact and advancing the workflow.

Core Features & Use Cases

  • Sequential artifact creation: automatically selects and creates the next artifact in an OpenSpec change.
  • Status-aware orchestration: reads current artifacts status to determine what can be created next.
  • Dependency-aware: reads completed dependencies to inform the new artifact.
  • Use Case: teams can resume stalled work by progressing to the next design or task artifact with minimal friction.

Quick Start

Select the change to continue and allow the system to create the next artifact.

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 creating the next artifact in an OpenSpec change workflow?

Automate OpenSpec change progression by selecting the target change; the system queries CLI status, identifies the next sequential artifact, and writes it using the schema template. This resumes stalled work and enforces dependency constraints.

How does dependency-aware artifact generation work in OpenSpec?

Dependency-aware artifact generation reads completed dependencies within the OpenSpec change to inform the new artifact's content. The system enforces artifact order and interfaces with the CLI to ensure constraints are respected.

Can I resume stalled OpenSpec changes by progressing to the next design or task artifact?

Resume stalled OpenSpec changes by selecting the change to continue. The system reads current artifact status and automatically generates the next design or task artifact, advancing the workflow with minimal friction.

What's the best way to enforce artifact order when managing OpenSpec changes?

Enforce OpenSpec artifact order by using status-aware orchestration that queries the CLI for current progress. The system determines what can be created next and writes the new artifact only when dependency constraints are met.

Does the OpenSpec CLI need to be installed to generate the next artifact in a change workflow?

The OpenSpec CLI is required to query artifact status and determine the next step in the workflow. The system interfaces with the CLI to read current progress and write new artifacts using the schema's template.

Why does my OpenSpec change workflow not advance to the next artifact automatically?

OpenSpec changes may stall if dependencies are incomplete or artifact status is not properly queried. The system reads CLI status to determine what can be created next, enforcing order and dependency constraints before writing.