openspec-continue-change

Creates the next OpenSpec change artifact by following the schema-driven workflow status.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-continue-change-thewoolleyman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/thewoolleyman/personal-knowledge-base/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-continue-change-thewoolleyman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on spec-driven changes with OpenSpec, it is easy to lose track of which artifact comes next (proposal, specs, design, tasks). This Skill inspects the current change status and creates exactly the next required artifact, keeping the workflow moving without manual bookkeeping. ## Core Features & Use Cases - Status-aware progression: Runs openspec status to determine which artifacts are done, ready, or blocked before acting. - Guided artifact creation: Fetches per-artifact instructions, templates, and dependency context from the OpenSpec CLI, then writes the artifact to the correct output path. - Interactive change selection: Lists recent changes and prompts the user to pick one when no change name is given, avoiding wrong guesses. - Use Case: You drafted a proposal for a new feature yesterday. Ask to continue the change, and the Skill reads the proposal, generates the capability spec files, and reports progress (e.g., 2/5 artifacts complete). ## Quick Start Ask the assistant to continue your OpenSpec change, optionally naming the change, and it will create the next pending artifact for you.

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 after creating the proposal?▼

Ask to continue the change and the Skill runs openspec status to find the first artifact marked ready, fetches its instructions and template, then writes that artifact. It creates exactly one artifact per invocation and reports updated progress.

What artifacts does the spec-driven OpenSpec workflow create?▼

The spec-driven schema produces a proposal, one spec file per capability listed in the proposal, a design document, and a tasks breakdown. Other schemas follow the instruction field returned by the openspec CLI instead.

Does this Skill require the openspec CLI to be installed?▼

Yes, the Skill depends on the openspec CLI for all operations including listing changes, checking status, and retrieving artifact instructions. Without the CLI installed and available on the PATH, the workflow cannot proceed.

What happens if I don't specify which change to continue?▼

The Skill runs openspec list to show the most recently modified changes and prompts you to select one, marking the most recent as recommended. It never auto-selects or guesses a change on its own.

Why does the Skill only create one artifact per invocation?▼

Creating one artifact at a time is a deliberate guardrail that keeps artifacts in schema order, lets you review each output before proceeding, and ensures dependency artifacts are read before the next one is written.