skills.rest
aniwei
aniweiCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Generate the next OpenSpec change artifact using the OpenSpec CLI.

Updated Feb 3, 2026
Search Tags:#automation#workflow#cli#openspec#artifact#change-management
One-click install
npx skills add https://github.com/aniwei/vitamin-code --skill openspec-continue-change-aniwei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/aniwei/vitamin-code/tree/main/refs/opencode/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/aniwei/vitamin-code --skill openspec-continue-change-aniwei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates continuing an OpenSpec change by generating the next artifact, enabling teams to progress their OpenSpec workflow with minimal manual intervention.

Core Features & Use Cases

  • Continue an OpenSpec change by creating the next required artifact in the sequence.
  • Automatically consult the OpenSpec CLI to list changes, check status, and generate the next artifact based on the active schema.
  • Use case: you want to advance a change named "user-auth" by producing its next artifact and moving the workflow forward.

Quick Start

Ask me to continue an OpenSpec change. If you have multiple changes, I will prompt you to choose which change to continue, then 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 continue an OpenSpec change and generate the next artifact?▼

You can automate OpenSpec change continuation by prompting the workflow to generate the next artifact. It checks completed dependencies, enforces artifact order based on the active schema, and writes the output using the CLI.

How does the OpenSpec workflow enforce artifact ordering when progressing a change?▼

The OpenSpec CLI enforces artifact order by reading the active schema and checking completed dependencies. It ensures the next artifact is only generated when prior sequence requirements are met.

Can I use this to automate OpenSpec change management across multiple active workflows?▼

Yes, you can automate OpenSpec change management across multiple workflows. If several changes exist, the Skill prompts you to select the target change before generating the next artifact.

What happens if I have multiple OpenSpec changes and want to advance one?▼

If you have multiple OpenSpec changes, the automation prompts you to choose which specific change to continue. It then queries the CLI for that change's status and generates the next artifact.

Do I need the OpenSpec CLI to generate the next artifact in my change sequence?▼

Yes, the OpenSpec CLI is required to list changes, check status, and generate the next artifact based on the active schema. The automation relies on the CLI to write artifacts to the output paths.

Related Skills

Explore More Software Engineering Skills→
artagonartagon

openspec-ff-change

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

Official
Intermediate
pradyumnasagarpradyumnasagar
6

roadmap-author

Guide authors through creating and validating ORS SKILL.md files.

Community
Intermediate
pabloimrik17pabloimrik17

openspec-continue-change

Create the next required OpenSpec artifact and advance change workflow via CLI.

Community
Intermediate
cenmiaocenmiao

openspec-continue-change

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

Community
Intermediate