skills.rest
GQAdonis
GQAdonisCOMMUNITY
Explore all skills by this author →
Website𝕏@gqadonisctoGitHub

openspec-continue-change

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

Updated Feb 16, 2026
Search Tags:#planning#spec-driven#cli#openspec#artifact generation#change workflow
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-continue-change-gqadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-continue-change
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-continue-change-gqadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of progressing an OpenSpec change by inspecting the current workflow state and creating exactly the next required artifact in the correct order. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to parse artifact states (ready, blocked, done) and picks the first ready artifact to create. - Instruction-Guided Authoring: Fetches per-artifact templates, rules, and dependency context via openspec instructions before writing files to the resolved output path. - Multi-Store Support: Discovers registered OpenSpec stores with openspec store list and applies a sticky --store flag across all scoped commands. - Use Case: A developer mid-way through a spec-driven change asks to continue; the skill selects the active change, generates the next artifact (e.g., a design doc), and reports progress (e.g., 3/5 complete). ## 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 skill with an optional change name; it runs openspec status to find the first artifact marked ready, fetches its instructions, and creates that single artifact. If no name is given, it infers the change from context or prompts you to select one.

How does the skill decide which artifact to create next?▼

It parses the JSON from openspec status and selects the first artifact with status ready, following the schema's defined sequence. It never skips artifacts or creates them out of order.

Does openspec-continue-change support multiple OpenSpec stores?▼

Yes. It runs openspec store list --json to discover registered stores, then appends a sticky --store flag to all scoped commands like status, instructions, and list for the rest of the workflow.

What happens when all planning artifacts are complete?▼

When isPlanningComplete is true, the skill stops creating artifacts, congratulates the user, shows the final status with the schema used, and suggests implementing and then archiving the change.

Why does the skill re-read dependency files from disk?▼

Dependency artifacts may have been edited since they were last seen in conversation, so the skill always re-reads them from disk before creating a new artifact to ensure the output reflects current content.

Related Skills

Explore More Software Engineering Skills→
sap-tutorialssap-tutorials
7

openspec-propose

Generates complete OpenSpec change proposals with design, specs, and task artifacts.

Official
Intermediate
captaincontratcaptaincontrat

openspec-archive-change

Archives completed OpenSpec changes with metadata preservation using the openspec CLI.

Official
Advanced
llama-farmllama-farm
2

openspec-continue-change

Create the next OpenSpec change artifact based on workflow status.

Official
Intermediate
tungnguyen10tungnguyen10

openspec-continue-change

Identify and generate the next schema-compliant artifact in OpenSpec change workflows.

Community
Intermediate