openspec-continue-change

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

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-continue-change-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-continue-change-codercoco-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a multi-artifact OpenSpec change (proposals, specs, tasks), it is easy to lose track of which artifact comes next and what structure it should follow. This Skill inspects the current change status and creates exactly the next ready artifact, keeping the workflow moving without manual bookkeeping. ## 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. - Template-guided artifact creation: Fetches per-artifact instructions, templates, and dependency files via openspec instructions, then writes the artifact to the resolved output path. - Change selection and store support: Infers the active change from context, prompts with recently modified changes when ambiguous, and supports named OpenSpec stores via --store flags. - Use Case: You have an in-progress spec-driven change with a completed proposal. Ask to continue, and the Skill reads the proposal from disk, generates the next artifact (e.g., design or tasks) from the schema template, and reports progress. ## Quick Start Ask the assistant to continue 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?

Invoke the continue command with an optional change name. The Skill runs openspec status to find the first artifact marked ready, fetches its instructions and template, and creates that single artifact before stopping.

How does the Skill pick which change to work on?

It uses a provided name, infers from conversation context, or auto-selects when only one active change exists. If ambiguous, it lists the most recently modified changes via openspec list --json and asks you to choose.

Does openspec-continue-change require the openspec CLI?

Yes, the openspec CLI must be installed and available. All status checks, instruction retrieval, and change listing are executed through openspec commands, and store-aware operations use the --store flag.

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 waits for you to ask it to continue again.

What happens when all artifacts in a change are complete?

When openspec status reports isComplete as true, the Skill stops without creating anything. It shows the final status and suggests implementing the change or archiving it.