openspec-continue-change

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

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/ValorVie/settingZsh --skill openspec-continue-change-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/ValorVie/settingZsh/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/ValorVie/settingZsh --skill openspec-continue-change-valorvie

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 guesswork. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to determine which artifact is ready, then generates it using the schema's 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. - Schema-Aware Artifact Creation: Supports spec-driven workflows (proposal, specs, design, tasks) and follows the instruction field for other schemas. - Use Case: You have an OpenSpec change with a completed proposal and want the spec files generated. Invoke this Skill, and it reads the proposal's Capabilities section, creates the next spec artifact, and reports progress. ## Quick Start Ask the assistant to continue working on your OpenSpec change and create the next artifact for the change you name.

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 and create the next artifact?▼

Invoke this Skill with a change name, or let it list recent changes via `openspec list --json` so you can pick one. It checks status with `openspec status --change <name> --json`, then creates the first artifact marked as ready.

What artifacts does the OpenSpec spec-driven workflow create?▼

The spec-driven schema produces a proposal, one spec per capability listed in the proposal, a design document, and a tasks file. Other schemas define their own sequences, which the Skill follows using the instruction field from the CLI.

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

Yes, the openspec CLI is a hard requirement. The Skill runs commands like `openspec list`, `openspec status`, and `openspec instructions`, so the CLI must be available in the environment before use.

Can the Skill 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 what was unlocked, then stops so you can review before continuing.

What happens if all artifacts in my OpenSpec change are complete?▼

The Skill detects `isComplete: true` in the status output, congratulates you, and suggests implementing or archiving the change. It does not create any further artifacts once the workflow is finished.