openspec-continue-change

Name: openspec-continue-change
Availability: InStock
Author: max-loo

Create the next OpenSpec change artifact after checking status and dependencies.

2|Updated Oct 13, 2025

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

Ready to run

npx skills add https://github.com/Max-Loo/multi-chat --skill openspec-continue-change-max-loo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Max-Loo/multi-chat/tree/main/.trae/skills/openspec-continue-change
Command: npx skills add https://github.com/Max-Loo/multi-chat --skill openspec-continue-change-max-loo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continuation of an OpenSpec change by creating the next artifact, enabling rapid progression of ongoing work.

Core Features & Use Cases

Orchestrates the continuation flow by selecting a change, checking its status, and generating the next artifact according to the active schema.
Reads dependency artifacts and applies guardrails to ensure correct sequencing and contextual consistency.
Provides clear outputs about which artifact was created and what unlocks next, supporting iterative development of OpenSpec changes.

Quick Start

Ask me to continue the OpenSpec change to create the next artifact.

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?▼

To continue an OpenSpec change, the workflow selects your active change, checks its status using openspec status, and generates the subsequent artifact by applying the active schema and reading dependency artifacts.

What is the best way to ensure correct sequencing when creating OpenSpec artifacts?▼

The best way to ensure correct sequencing is using a guided workflow that applies guardrails, reads dependency artifacts, and enforces order to maintain contextual consistency across your OpenSpec changes.

How does the OpenSpec change management workflow communicate progress?▼

The OpenSpec change management workflow communicates progress by providing clear outputs about which artifact was created and what unlocks next, supporting iterative development throughout the continuation flow.

Do I need to manually check dependencies before progressing an OpenSpec change?▼

You do not need to manually check dependencies because the workflow automatically reads dependency artifacts and applies guardrails to ensure correct sequencing and contextual consistency before generating the next artifact.

What happens after the next OpenSpec artifact is created?▼

After the next OpenSpec artifact is created, the workflow provides clear outputs detailing the newly generated artifact and indicating exactly what subsequent actions or artifacts unlock next in the change sequence.