openspec-continue-change

Create the next OpenSpec change artifact according to workflow state.

Updated Jan 29, 2026

Search Tags:#automation #workflow #cli #openspec #artifact #change-management

Ready to run

npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-continue-change-hongquandev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/hongquandev/OpenSpec-VI/tree/main/.agent/skills/openspec-continue-change
Command: npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-continue-change-hongquandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continued workflow for OpenSpec changes by generating the next artifact, enabling iterative development without restarting from scratch.

Core Features & Use Cases

Artifact progression: guides you through selecting the relevant change, validating status, and producing the next artifact according to the active schema.
Guarded workflow: ensures dependencies are read before creation and enforces single-artifact-per-call rules to prevent missteps.
Use Case: when you want to evolve a change, generate the next artifact, or advance your OpenSpec workflow through its stages (proposal, specs, design, tasks).

Quick Start

Continue the OpenSpec change by creating the next artifact according to the current workflow state.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema

How do I generate the next artifact in an OpenSpec change workflow?▼

To generate the next OpenSpec artifact, the workflow automation reads existing dependencies, validates the current change status, and produces the single next artifact required by the active schema.

What is the best way to automate OpenSpec change progression across schemas?▼

Automating OpenSpec change progression involves selecting the relevant change, honoring the predefined artifact order, and applying CLI guidance to advance the workflow through its stages without restarting.

Can I create multiple artifacts in a single OpenSpec workflow operation?▼

No, the OpenSpec change workflow enforces single-artifact-per-call rules to prevent missteps, meaning only one artifact is produced per operation to maintain strict guardrails.

Do I need to read dependencies before advancing an OpenSpec change?▼

Yes, the guarded workflow ensures dependencies are read before artifact creation, validating the current state and applying CLI guidance to safely produce the next artifact in the sequence.

Why does my OpenSpec change workflow not advance to the proposal stage?▼

An OpenSpec change workflow will not advance if prior dependencies are missing or the artifact order is not honored, as the automation enforces guardrails by validating status before generating the next artifact.

What stages can I advance through when evolving an OpenSpec change?▼

Evolving an OpenSpec change advances the workflow through proposal, specs, design, and tasks stages, generating the next required artifact iteratively according to the active schema.