skills.rest
thelegendtubaguy
thelegendtubaguyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Generate the next OpenSpec artifact file for a selected change.

33|5|Updated Feb 24, 2026
Search Tags:#automation#workflow#openspec#change-management#artifact-generation
One-click install
npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-continue-change-thelegendtubaguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized/tree/main/.pi/skills/openspec-continue-change
Command: npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-continue-change-thelegendtubaguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue OpenSpec changes by creating the next artifact to progress a change workflow, enabling teams to move from planning to implementation in a controlled sequence.

Core Features & Use Cases

  • Guided continuation: prompts you to choose a change when not specified and presents recent changes with their status to decide which one to continue.
  • Status-driven artifact creation: checks the current progression, selects ready artifacts, and generates the next artifact file based on the instruction template, dependencies, and planning context.
  • Workflow automation: integrates with the OpenSpec CLI to drive the ongoing change lifecycle, ensuring artifacts are created in the correct order and unlocked for follow-up steps.

Quick Start

Prompt OpenSpec to list recent changes and select one to continue, then trigger the artifact-creation flow to advance that change.

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 and generate the next artifact?▼

To continue an OpenSpec change workflow, select an active change to check its current progression status, then generate the next artifact file in the defined sequence based on completed dependencies and the instruction template.

What is the process for status-driven artifact creation in a change management workflow?▼

Status-driven artifact creation checks the current workflow progression, identifies ready artifacts by reading completed dependencies, and writes the next artifact file in the correct order according to the planning context.

How do I select which OpenSpec change to continue when multiple are active?▼

When a specific change is not provided, the guided continuation flow prompts you to choose from a list of recent changes, displaying their current status to help you decide which change to advance.

Does the OpenSpec CLI support automated artifact generation for change management?▼

Yes, the OpenSpec CLI integrates with workflow automation to drive the ongoing change lifecycle, ensuring artifact files are created in the correct sequence and unlocked for follow-up steps.

How are artifact dependencies managed when progressing a change workflow?▼

Artifact dependencies are managed by reading completed prerequisite artifacts and only selecting and generating the next artifact file when its defined dependencies are met, ensuring a controlled sequence.

Related Skills

Explore More Software Engineering Skills→
zdpkzdpk

openspec-ff-change

Automates OpenSpec artifact generation from scaffolding to implementation-ready output.

Community
Advanced
081595081595

openspec-continue-change

Create the next artifact in an OpenSpec change lifecycle.

Community
Intermediate
remiverdiesenremiverdiesen
6

openspec-ff-change

Create OpenSpec implementation artifacts in dependency-aware order.

Community
Advanced
huangjia2019huangjia2019
114

openspec-new-change

Scaffold a new OpenSpec change with artifact-driven workflow templates.

Community
Intermediate