openspec-continue-change

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

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-continue-change-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-continue-change
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-continue-change-raphaelmans

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 ready artifact, keeping the planning process moving without manual guesswork. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to parse artifact states (ready, blocked, done) and picks the first artifact ready to be created. - Guided Artifact Creation: Fetches per-artifact instructions, templates, and dependency context from the CLI, then writes the artifact to the resolved output path. - Change Selection & Store Support: Infers the active change from context, prompts with recently modified changes when ambiguous, and supports registered OpenSpec stores via --store <id>. - Use Case: You have an OpenSpec change with a completed proposal and want the design document next. Ask to continue the change, and the Skill reads dependencies, applies the schema template, and writes the next artifact. ## 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 workflow?

Invoke the Skill with an optional change name, and it runs openspec status to find the first artifact marked ready. It then fetches instructions for that artifact and creates it, stopping after one artifact per invocation.

How does the Skill choose 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 and asks you to pick one.

Does this Skill require the openspec CLI installed?

Yes, the Skill depends entirely on the openspec CLI for status, instructions, list, and related commands. Without the CLI installed and an OpenSpec change present, it cannot create artifacts.

What happens when all planning artifacts are complete?

When the status reports isPlanningComplete as true, the Skill stops creating artifacts, shows the final status and schema used, and suggests implementing the change and archiving it afterward.

Can I use this with a registered OpenSpec store?

Yes, run openspec store list to discover registered store ids, then the Skill appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.