skills.rest
lstellway
lstellwayCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

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

Updated Nov 7, 2023
Search Tags:#spec-driven#cli#tasks#openspec#proposal#artifact generation#change workflow
One-click install
npx skills add https://github.com/lstellway/nixfiles --skill openspec-continue-change-lstellway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/lstellway/nixfiles/tree/main/modules/home-manager/claude/skills/openspec-continue-change
Command: npx skills add https://github.com/lstellway/nixfiles --skill openspec-continue-change-lstellway

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 (proposal, specs, design, tasks). 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 --json to determine which artifact is ready, then generates it using the CLI-provided template, context, and rules. - Interactive change selection: If no change name is given, lists recent changes via openspec list --json and prompts the user to pick one instead of guessing. - Guided artifact authoring: Reads completed dependency artifacts for context and writes the new artifact to the CLI-specified output path, one artifact per invocation. - Use Case: You drafted a proposal for a new feature change yesterday. Ask to continue the change, and the Skill detects the proposal is done, then generates the capability spec files that are now unlocked. ## Quick Start Ask the assistant to continue your OpenSpec change, optionally naming the change, and it will create the next pending 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 writes that artifact to the specified output path, one per invocation.

What artifacts does the spec-driven schema create?▼

The spec-driven schema produces a proposal, one spec file per capability listed in the proposal, a design document, and a tasks breakdown. The Skill follows the schema's artifact sequence from the CLI rather than assuming fixed names.

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 with JSON output to drive every step of the workflow.

What happens if I don't specify a change name?▼

The Skill runs openspec list --json and prompts you to choose from the most recently modified changes, marking the newest as recommended. It never auto-selects or guesses a change on its own.

Why does the Skill only create one artifact per run?▼

Creating one artifact per invocation keeps each output reviewable and ensures dependency artifacts are read before the next one is generated. After each creation it shows progress and what is newly unlocked.

Related Skills

Explore More Software Engineering Skills→
JanuaryLabsJanuaryLabs
4

openspec-new-change

Scaffold OpenSpec change directories and retrieve the first artifact template.

Official
Intermediate
jankneumannjankneumann
4

openspec-onboard

Guide users through the OpenSpec workflow cycle with CLI commands.

Community
Intermediate
gabrielnsmntogabrielnsmnto
3

qa-review-proposal

Review modification proposals with code quality, conflict, and security analysis.

Community
Advanced
dorriodorrio

openspec-apply-change

Implement OpenSpec change tasks and update artifacts via the openspec CLI.

Community
Advanced