openspec-continue-change

Creates the next artifact for an OpenSpec change using the openspec CLI.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-continue-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-continue-change-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through an OpenSpec change workflow, it is hard to know which artifact comes next, what template it should follow, and which dependencies must be read first. This Skill automates that progression by querying the openspec CLI for status and instructions, then creating exactly one ready artifact per invocation. ## Core Features & Use Cases - Change Selection: Infers the active change from context, auto-selects when only one exists, or prompts with the most recently modified changes when ambiguous. - Status-Driven Progression: Parses openspec status JSON to find the first artifact with ready status and retrieves its template, rules, and dependencies via openspec instructions. - Guarded Artifact Creation: Re-reads dependency files from disk, applies context and rules as constraints without copying them into output, and verifies the artifact exists before reporting progress. - Use Case: You have an OpenSpec change with a completed proposal and want the next artifact (e.g., design or tasks) generated correctly. Invoke this Skill and it creates that single artifact, then shows progress and what is now unlocked. ## Quick Start Ask the assistant to continue your OpenSpec change, optionally naming the change, and it will create the next ready 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 continue an OpenSpec change workflow?▼

Invoke this Skill with an optional change name. It runs openspec status to find the first artifact marked ready, fetches its instructions and template, creates that single artifact, and reports updated progress.

What happens if I have multiple active OpenSpec changes?▼

The Skill tries to infer the change from conversation context or auto-selects when only one exists. Otherwise it lists the most recently modified changes with status and asks you to pick one, marking the most recent as recommended.

Does this Skill require the openspec CLI installed?▼

Yes, the Skill depends on the openspec CLI being available, as declared in its compatibility metadata. All status checks, instruction retrieval, and artifact scaffolding go through openspec commands.

Can it create multiple artifacts in one run?▼

No, the guardrails explicitly limit each invocation to creating exactly one artifact. After creation it shows progress and unlocked artifacts, then stops so you can review before continuing.

What is a store in OpenSpec and how is it handled?▼

A store is a standalone OpenSpec repo registered on the machine. If your work lives in one, the Skill discovers store ids via openspec store list and passes --store <id> on all subsequent read and write commands.