openspec-continue-change

Create the next artifact in an OpenSpec change workflow.

2.0k|254|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/Draculabo/AntigravityManager --skill openspec-continue-change-draculabo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Draculabo/AntigravityManager/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/Draculabo/AntigravityManager --skill openspec-continue-change-draculabo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue OpenSpec changes by automatically creating the next artifact in the workflow, ensuring consistent progression and reducing manual setup across multiple changes.

Core Features & Use Cases

  • Automatically generates the next artifact in an OpenSpec change when you want to progress.
  • Checks the current status, resolves dependencies, and applies the proper template/instructions to produce the artifact file.
  • Works with standard OpenSpec change workflows to maintain sequencing and consistency across artifacts.

Quick Start

Tell me the OpenSpec change name to continue, and I will generate the next artifact in the workflow.

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 artifact generation for OpenSpec change workflows?

Automating artifact generation for OpenSpec change workflows involves checking the current status, resolving dependencies, and applying templates to produce the next file. This ensures consistent progression and reduces manual setup across multiple changes.

What is the process for continuing an OpenSpec change with the next artifact?

Continuing an OpenSpec change requires sequencing artifacts by their dependencies and consulting instruction templates. The process creates one artifact per invocation while respecting the established workflow order.

How do I ensure dependency order is respected when creating OpenSpec artifacts?

Respecting dependency order when creating OpenSpec artifacts requires checking the current change status first. The workflow resolves dependencies and applies the proper template to generate the artifact file in the correct sequence.

Can I generate multiple OpenSpec artifacts in a single workflow invocation?

Generating multiple OpenSpec artifacts in a single invocation is not supported. The workflow creates one artifact per invocation to ensure dependency order is respected and templates are properly applied.

Do I need to manually select templates when progressing OpenSpec change workflows?

Manually selecting templates when progressing OpenSpec change workflows is unnecessary. The system automatically consults instruction templates and resolves dependencies to produce the correct artifact file.

Why does my OpenSpec change workflow stop progressing between artifacts?

OpenSpec change workflows stop progressing when the next artifact has not been generated. Resolving dependencies and applying the proper template for the next artifact in the sequence resumes the workflow.