openspec-continue-change

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

1|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/phuchoang2603/nixos --skill openspec-continue-change-phuchoang2603
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/phuchoang2603/nixos/tree/main/home/base/cli/skills/openspec-continue-change
Command: npx skills add https://github.com/phuchoang2603/nixos --skill openspec-continue-change-phuchoang2603

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through an OpenSpec change, it is easy to lose track of which artifact comes next in the schema workflow. This Skill inspects the change status, picks the next ready artifact, and creates it correctly so the planning workflow keeps moving without manual guesswork. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to parse artifact states (done, ready, blocked) and selects the first ready artifact to create. - Instruction-Guided Authoring: Fetches per-artifact templates, rules, and context via openspec instructions, then writes the artifact to the resolved output path. - Store-Aware Operation: Supports registered OpenSpec stores by discovering store ids and applying the --store flag consistently across commands. - Use Case: You have a spec-driven change with a completed proposal but no tasks file. Invoke this Skill and it reads the proposal from disk, follows the schema instructions, and writes tasks.md, then reports progress and what is now unlocked. ## Quick Start Ask the assistant to continue working on your OpenSpec change and create the next artifact for the change you name.

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?▼

Invoke the Skill with an optional change name. It runs openspec status to find the first artifact with ready status, fetches its instructions, and writes the artifact to the resolved output path, creating exactly one artifact per invocation.

What happens if I don't specify a change name in OpenSpec?▼

The Skill infers the change from conversation context or auto-selects when only one active change exists. If ambiguous, it runs openspec list --json and prompts you with the most recently modified changes, marking the newest as recommended.

Does this Skill work with OpenSpec stores?▼

Yes. If you name a store, it runs openspec store list --json to discover registered store ids, then appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.

What are the requirements for using the openspec-continue-change Skill?▼

You need the openspec CLI installed and an existing OpenSpec change with a schema workflow. The Skill only uses Bash openspec commands and operates on the nearest local openspec root unless a store is selected.

Why does the Skill stop after creating one artifact?▼

It is a deliberate guardrail: one artifact per invocation keeps the schema sequence intact, prevents out-of-order creation, and lets you review each artifact before continuing to the next step.