skills.rest
8007342
8007342COMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Creates the next artifact for an OpenSpec change using the openspec CLI.

5|Updated Mar 21, 2026
Search Tags:#planning#spec-driven#change management#openspec#artifact generation#cli workflow
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-continue-change-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-continue-change-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of advancing an OpenSpec change by checking the change's status, identifying the next ready artifact, and creating it according to the schema's instructions. ## 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. - Schema-guided artifact creation: Fetches per-artifact instructions, templates, and dependency files via openspec instructions, then writes the artifact to the resolved output path. - Store-aware workflows: Supports registered OpenSpec stores by discovering them with openspec store list --json and applying a sticky --store <id> flag to all scoped commands. - Use Case: After drafting a proposal for a spec-driven change, ask the assistant to continue; it reads the proposal from disk, generates the next artifact (such as design or tasks), and reports progress. ## Quick Start Ask the assistant to continue working on your OpenSpec change, optionally naming the change or store to use.

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

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 do I work with an OpenSpec store instead of a local repo?▼

Run openspec store list --json to discover registered store ids, then pass --store <id> on commands like status, instructions, and list. The selected store flag stays sticky for the rest of the workflow.

What happens when all OpenSpec planning artifacts are complete?▼

When isPlanningComplete is true, the skill stops creating artifacts, shows the final status and schema used, and suggests implementing the change and archiving it once tracked work is done.

Does this skill create multiple artifacts at once?▼

No, it creates exactly one artifact per invocation and then stops. It also never skips artifacts or creates them out of order, following the sequence defined by the change's schema.

What are the requirements for using openspec-continue-change?▼

You need the openspec CLI installed and an existing OpenSpec change, either in a local openspec/ root or a registered store. The skill only invokes openspec commands and writes artifact files to paths the CLI resolves.

Related Skills

Explore More Software Engineering Skills→
joannanowakowskajoannanowakowska

openspec-continue-change

Create the next required artifact in an OpenSpec change workflow.

Community
Advanced
wishx127wishx127

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts and task status.

Community
Advanced
Chorus-AIDLCChorus-AIDLC
1.2k

openspec-propose

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

Official
Intermediate
linaproailinaproai
147

openspec-propose

Generate proposal, design, and task artifacts via the openspec CLI.

Official
Advanced