skills.rest
wonderslife
wonderslifeCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Create the next OpenSpec change artifact using the schema template.

13|3|Updated Apr 7, 2026
Search Tags:#automation#workflow#schema#openspec#artifact#change-management
One-click install
npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill openspec-continue-change-wonderslife
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/openspec/openspec-continue-change
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill openspec-continue-change-wonderslife

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue OpenSpec changes efficiently by automatically creating the next artifact in the sequence, reducing manual steps and error-prone handoffs.

Core Features & Use Cases

  • Identify the next artifact to create based on the active schema and current dependency status.
  • Integrate completed dependency artifacts to maintain context and chain workflow.
  • Generate the artifact using the schema-provided template and write it to the specified path.
  • Use Case: When a user wants to progress a change after the previous artifact is completed and validated.

Quick Start

Continue the OpenSpec change by creating the next artifact using the current schema and any completed dependencies.

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

To continue an OpenSpec change, the skill identifies the next artifact based on the active schema, validates completed dependency artifacts, and writes the new artifact to your specified path using a template.

What is the best way to automate OpenSpec change progression through a multi-artifact workflow?▼

Automating OpenSpec change progression involves selecting ready artifacts, fetching schema instructions, validating dependencies, and generating the new artifact automatically to reduce manual steps and error-prone handoffs.

How does dependency validation work when creating OpenSpec schema artifacts?▼

Schema artifact dependency validation checks completed dependency artifacts to maintain context and chain the workflow, ensuring that prerequisite artifacts are successfully integrated before generating the next one.

Can I use a custom template to write an OpenSpec artifact to a specific path?▼

Yes, artifact generation uses the schema-provided template to write output to the specified path, ensuring compliant artifact creation guided by the schema instruction while respecting workflow dependencies.

What should I do if my OpenSpec change is not progressing to the next artifact?▼

If your OpenSpec change is not progressing, verify that previous dependency artifacts are completed and validated, as the workflow requires validated dependencies before selecting and fetching instructions for the next artifact.

When do I need to use an automated workflow for OpenSpec change management?▼

You need automated change management when a change requires progression through a multi-artifact workflow, allowing you to select ready artifacts, integrate dependencies, and generate new schema-compliant artifacts efficiently.

Related Skills

Explore More Software Engineering Skills→
rm-rf-etcrm-rf-etc

openspec-continue-change

Create the next artifact in an OpenSpec change workflow.

Community
Advanced
Max-LooMax-Loo
2

openspec-new-change

Scaffold a new OpenSpec change with schema-aware artifact prompts.

Community
Advanced
gmf520gmf520
17

openspec-new-change

Scaffold OpenSpec changes and fetch the first artifact template.

Community
Intermediate
PBH-BTNPBH-BTN
6.2k

openspec-continue-change

Generate the next OpenSpec workflow artifact via the OpenSpec CLI.

Official
Advanced