skills.rest
rockdong
rockdongCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Create the next OpenSpec change artifact based on current status.

Updated Dec 31, 2025
Search Tags:#automation#workflow#cli#openspec#artifact#prompt#change-management
One-click install
npx skills add https://github.com/rockdong/stock_for_cpp --skill openspec-continue-change-rockdong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/rockdong/stock_for_cpp/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/rockdong/stock_for_cpp --skill openspec-continue-change-rockdong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams progress OpenSpec changes by automatically generating the next artifact, ensuring a smooth transition between stages.

Core Features & Use Cases

  • Prompts for a change name when ambiguous, selecting the most relevant change to continue.
  • Checks current status of artifacts, dependencies, and progress to determine what to create next.
  • Generates the next artifact file according to the active schema (spec-driven or others) and updates progress.
  • Provides visibility into unlocked artifacts and next steps after each operation.

Quick Start

Prompt the user to specify a change name when ambiguous, then progress by checking status and creating the next artifact according to the active schema.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema
How do I automate creating the next artifact in an OpenSpec change workflow?▼

Automate OpenSpec change progression by evaluating current artifact status and dependencies via CLI prompts to generate the next artifact file. This ensures correct sequencing and context-aware output for smooth stage transitions.

What happens if my OpenSpec change name is ambiguous when continuing artifacts?▼

When the OpenSpec change name is ambiguous, the workflow prompts you to specify the change name. It then selects the most relevant change to continue by evaluating current artifact dependencies and progress.

How does artifact sequencing determine what to create next in change management?▼

Artifact sequencing determines the next step by checking current status, dependencies, and progress. It applies guarded logic to generate the correct artifact template or prompt based on the active schema and current change state.

Can I use CLI prompts to manage OpenSpec change status and progress?▼

Yes, you can use CLI-driven prompts to check current artifact status and dependencies. This manages OpenSpec change progress by evaluating the state and automatically generating the next required artifact file.

Does OpenSpec change continuation support spec-driven artifact templates?▼

OpenSpec change continuation supports spec-driven artifact templates and other active schemas. It generates the next artifact file according to the active schema and updates progress after each operation.

Related Skills

Explore More Software Engineering Skills→
CatsofsufferingCatsofsuffering
5

openspec-new-change

Scaffold an OpenSpec change directory and validate kebab-case names.

Community
Intermediate
arestivoarestivo

openspec-continue-change

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

Community
Advanced
carlosapgomescarlosapgomes

openspec-continue-change

Continue an OpenSpec change by creating the next workflow artifact.

Community
Advanced
memorysavermemorysaver

openspec-onboard

Guide users through the OpenSpec change lifecycle with in-repo tasks.

Community
Advanced