openspec-continue-change

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

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-continue-change-twaananen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/twaananen/6dof-drone-sim/tree/main/.agents/skills/openspec-continue-change
Command: npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-continue-change-twaananen

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. This Skill inspects the current change status and creates exactly the next required artifact, keeping the workflow moving 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 schema-specific instructions, templates, and dependency context from the 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 yesterday and return today. Ask to continue, and the Skill detects the proposal is done, reads it as a dependency, and generates the next artifact such as a capability spec or design document. ## Quick Start Ask the assistant to continue working on your OpenSpec change, optionally naming the change you want to progress.

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?▼

Ask to continue the change, optionally providing its name. The Skill 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 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 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.

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 by design. After writing, it shows progress and what was unlocked, then waits for you to ask it to continue again.