skills.rest
cenmiao
cenmiaoCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Create the next OpenSpec workflow artifact from CLI status and dependencies.

Updated Mar 31, 2026
Search Tags:#automation#workflow#spec-driven#cli#openspec#artifact#change-management
One-click install
npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-continue-change-cenmiao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/cenmiao/openspec-pro/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/cenmiao/openspec-pro --skill openspec-continue-change-cenmiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams continue an in-progress OpenSpec change by selecting the correct change, inspecting its status, and creating the next required artifact so work can progress without manual orchestration of the spec workflow.

Core Features & Use Cases

  • Guided selection: Lists recent changes and prompts the user to choose which change to continue rather than guessing.
  • Status-driven action: Calls the openspec CLI to determine which artifact is ready, reads dependencies, and creates exactly one artifact following schema instructions and guardrails.
  • Use Case: A developer or product manager who has a draft proposal and needs the assistant to generate the next spec or design artifact in the project's workflow using the openspec CLI outputs.

Quick Start

Ask the assistant to continue the change named "my-feature" and create the next artifact using the openspec CLI.

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I advance an OpenSpec change to the next workflow artifact?▼

To advance an OpenSpec change, the Skill inspects CLI status outputs, parses JSON instructions, reads dependency files, and writes the next artifact to the specified output path while enforcing schema rules.

How do I generate the next spec artifact from openspec CLI outputs?▼

Generating the next spec artifact involves selecting an in-progress change, calling the openspec CLI to determine which artifact is ready, and creating exactly one artifact following the provided schema instructions and guardrails.

Do I need the openspec CLI to continue spec-driven change management?▼

Yes, you need the openspec CLI installed to continue spec-driven change management, because this Skill depends on its JSON outputs to determine artifact status, parse instructions, and identify dependencies.

What is the best way to automate sequential artifact creation for spec-driven workflows?▼

Automating sequential artifact creation is best handled by using CLI status outputs to drive decisions, ensuring the assistant creates exactly one artifact at a time based on parsed JSON instructions and dependency files.

Why does my OpenSpec change workflow require reading dependency files before writing artifacts?▼

Reading dependency files is required because the workflow enforces schema rules and guardrails, ensuring the newly created artifact correctly references existing dependencies and instructions parsed from the CLI status.

Related Skills

Explore More Software Engineering Skills→
psaccpsacc

openspec-ff-change

Generate OpenSpec change artifacts in dependency order until apply-ready.

Community
Intermediate
tonysyutonysyu
2

openspec-continue-change

Generate the next OpenSpec workflow artifact using the OpenSpec CLI.

Community
Advanced
arestivoarestivo

openspec-continue-change

Generate the next OpenSpec change artifact from CLI status and instructions.

Community
Advanced
wtg42wtg42

openspec-continue-change

Create the next OpenSpec change artifact from CLI status and dependencies.

Community
Intermediate