openspec-continue-change

Creates the next artifact in an OpenSpec change workflow using the openspec CLI.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-continue-change-joeshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/JoeShi/coding-agent-usage-montior/tree/main/.kimi-code/skills/openspec-continue-change
Command: npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-continue-change-joeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through an OpenSpec change, it is hard to know which artifact comes next, what its required structure is, and which dependencies must be read first. This Skill inspects the change status and creates exactly the next ready artifact in the correct order. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to parse artifact states (done, ready, blocked) and picks the first ready artifact to create. - Instruction-Guided Authoring: Fetches per-artifact templates, rules, and dependency context via openspec instructions, then writes the artifact to the resolved output path. - Multi-Store Support: Discovers registered OpenSpec stores with openspec store list --json and applies a sticky --store <id> flag to all scoped commands. - Use Case: You have a change with a completed proposal and want the design document next. Invoke the Skill, and it reads the proposal from disk, follows the schema's template and rules, and writes the design artifact without skipping steps. ## 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 marked ready, fetches its instructions and template, reads completed dependency files, and writes one artifact to the resolved output path.

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 multiple OpenSpec stores?

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

Can it create multiple OpenSpec artifacts in one run?

No. The Skill creates exactly one artifact per invocation and then stops, showing progress and what was unlocked. This guardrail prevents skipping artifacts or creating them out of schema order.

What are the requirements for using this OpenSpec Skill?

You need the openspec CLI installed and an existing change with artifacts in a ready state. The Skill only invokes openspec commands and writes artifact files; it does not install tooling or modify specs directly.