openspec-continue-change

Guide creation of the next OpenSpec workflow artifact via CLI steps.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/kunish/muon --skill openspec-continue-change-kunish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/kunish/muon/tree/main/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/kunish/muon --skill openspec-continue-change-kunish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continues OpenSpec changes by guiding the creation of the next artifact, helping teams progress a change without losing context.

Core Features & Use Cases

  • Guides the user through selecting the next artifact to create based on the current workflow state.
  • Reads the current change status, fetches artifact instructions, and generates the required artifact at the specified output path.
  • Supports standard OpenSpec workflows and enforces proper sequencing and guardrails to avoid out-of-order artifacts.

Quick Start

Tell me to continue the OpenSpec change to generate 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 workflow artifact?

To continue an OpenSpec change, invoke the workflow guidance to read the current change status, select the next artifact, and generate it at the specified output path. This enforces CLI-based steps and proper sequencing to avoid out-of-order artifacts.

What is the OpenSpec change workflow and when do I need to create artifacts?

The OpenSpec change workflow is a structured process for progressing changes through sequenced artifacts. You need to create artifacts when advancing a change, ensuring context is maintained and proper guardrails prevent out-of-order generation.

How do I guide my team through selecting the next artifact in an OpenSpec change?

Guide artifact selection by reading the current change status and fetching artifact instructions through CLI-based steps. The workflow prompts for selection and writes the required artifact to the specified output path while respecting context and rules.

Can I use CLI automation to advance an OpenSpec workflow without losing context?

Yes, CLI automation advances OpenSpec workflows by reading change status, prompting for artifact selection, and writing outputs to specified paths. It enforces sequencing and guardrails to progress changes without losing context.

Why does my OpenSpec change workflow enforce artifact sequencing and guardrails?

OpenSpec change workflows enforce artifact sequencing and guardrails to prevent out-of-order artifact generation. This ensures proper workflow progression, maintains context, and validates that each artifact follows the correct process steps.

What are the limitations of automating OpenSpec change artifact generation via CLI?

Automating OpenSpec artifact generation via CLI requires strict adherence to workflow sequencing and guardrails. Out-of-order artifacts are blocked, and the process depends on reading current change status and fetching instructions before writing outputs to specified paths.