openspec-continue-change

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

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-continue-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/zh-impact/agent-feeder/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-continue-change-zh-impact

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 in the workflow. This Skill inspects the current change status and creates exactly the next required artifact, keeping the proposal-to-tasks pipeline moving without manual bookkeeping. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to determine which artifact is ready, then generates it using the CLI-provided template, context, and rules. - Interactive Change Selection: Lists recent changes via openspec list --json and prompts the user to pick one when no change name is given, never guessing. - Schema-Aware Artifact Creation: Supports spec-driven workflows (proposal, specs, design, tasks) and follows the instruction field for other schemas. - Use Case: You drafted a proposal yesterday and return today. 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 working on your OpenSpec change and create the next artifact for the change you are working on.

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, optionally naming it. The Skill runs openspec status to find the first artifact marked ready, fetches its instructions and template, then creates that single artifact 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.

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

Yes, the openspec CLI is required. The Skill shells out to commands like openspec list, openspec status, and openspec instructions to determine state and retrieve artifact templates, so it cannot function without the CLI.

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

The Skill runs openspec list --json and prompts you to choose from the most recently modified changes, marking the newest as recommended. It never auto-selects or guesses a change on its own.

Can it create multiple artifacts in one run?▼

No, it creates exactly one artifact per invocation by design. After writing the artifact it shows progress and what was unlocked, then stops so you can review before continuing.