openspec-continue-change

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

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-continue-change-capella-hotel-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/capella-hotel-group/capella-hotel-group-poc/tree/main/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-continue-change-capella-hotel-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a spec-driven change 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 --change <name> --json to determine which artifacts are done, ready, or blocked before acting. - Guided artifact creation: Fetches per-artifact instructions, templates, and dependency context via openspec instructions, then writes the artifact to the correct output path. - Interactive change selection: When no change name is given, lists recent changes via openspec list --json and prompts the user to pick one. - Use Case: You drafted a proposal for a new feature yesterday. Ask the assistant to continue the change, and it reads the proposal, generates the capability spec files, and reports progress (e.g., 2/4 artifacts complete). ## Quick Start Ask the assistant to continue working on your OpenSpec change, optionally naming the change, and it will create the next 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 workflow?▼

Ask the assistant to continue the change, optionally providing the change name. It runs openspec status to find the first artifact marked ready, fetches its instructions and template, and writes that single artifact to the specified output path.

What artifacts does the spec-driven schema create?▼

The spec-driven schema produces a proposal.md, one spec.md per capability under specs/, a design.md, and a tasks.md. Each capability listed in the proposal gets its own spec file named after the capability, not the change.

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

The skill runs openspec list --json and prompts you to select from the most recently modified changes, showing schema, task status, and modification time. It never auto-selects or guesses a change on your behalf.

Does this skill require the openspec CLI installed?▼

Yes, the openspec CLI is a hard requirement. All status checks, instruction retrieval, and change listing are performed through openspec commands, so the CLI must be available in the environment.

Can it create multiple artifacts in one run?▼

No, it creates exactly one artifact per invocation and then stops. After writing, it shows progress and what was unlocked, and you can ask it to continue again for the next artifact.