openspec-continue-change

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

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-continue-change-germainlefebvre4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/germainlefebvre4/cvwonder-forms/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-continue-change-germainlefebvre4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through an OpenSpec change, it is hard to know which artifact comes next, what its required structure is, and which dependencies must be read first. This Skill automates that progression by querying the openspec CLI for status and instructions, then creating exactly one correctly-structured artifact per invocation. ## Core Features & Use Cases - Change Selection: Infers the active change from context or lists recent changes with status and schema so the user can pick one. - Status-Driven Progression: Parses openspec status --json to find the first ready artifact and retrieves its template, rules, and dependencies via openspec instructions. - Guardrailed Artifact Creation: Re-reads dependency files from disk, applies context and rules as constraints without copying them into output, and verifies the artifact exists before reporting progress. - Use Case: A developer has a proposal artifact done and asks to continue; the Skill detects the next ready artifact (e.g., design or tasks), reads the proposal, writes the new file to the resolved output path, and shows updated progress. ## Quick Start Ask the assistant to continue your OpenSpec change, optionally naming the change, and it will create the next artifact in the workflow.

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 to the next artifact?

Invoke the continue workflow with an optional change name. 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 happens if I don't specify a change name in OpenSpec?

The Skill infers the change from conversation context or auto-selects it if only one active change exists. If ambiguous, it lists the most recently modified changes with schema and status so you can choose one.

Does this workflow require the openspec CLI installed?

Yes, the openspec CLI is required. All status checks, instruction retrieval, and change listing are performed through openspec commands such as status, instructions, and list with JSON output.

Can it create multiple OpenSpec artifacts in one run?

No, it creates exactly one artifact per invocation by design. After writing the artifact it shows progress and prompts you to continue, ensuring each artifact is built on freshly read dependencies.

Why does the Skill re-read dependency files from disk?

Dependency artifacts may have been edited since they were last seen in conversation. Re-reading from disk guarantees the new artifact is based on the current file contents rather than stale context.