openspec-continue-change

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

Updated Apr 20, 2020
One-click install
npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-continue-change-unterrainerinformatik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/UnterrainerInformatik/java-rdb-utils/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-continue-change-unterrainerinformatik

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 workflow. This Skill inspects the current change status and creates exactly the next required artifact, keeping the spec-driven workflow moving forward 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, never guessing. - Use Case: You drafted a proposal for a new feature change yesterday. Ask to continue the change, and the Skill reads the proposal, generates the next artifact (such as capability specs), and reports progress like "2/4 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 workflow?▼

Invoke the Skill with an optional change name. It runs openspec status to find the first artifact marked ready, fetches its instructions and template, then writes that single artifact to the specified output path.

What artifacts does the spec-driven schema create?▼

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

Does this Skill require the openspec CLI installed?▼

Yes, the Skill depends on the openspec CLI for listing changes, checking status, and retrieving artifact instructions. Without it, the workflow commands cannot run.

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, marking the newest as recommended. It never auto-selects or guesses a change.

Can it create multiple artifacts in one run?▼

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