openspec-continue-change

Create the next artifact for an OpenSpec change via the OpenSpec CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you continue an OpenSpec change by automatically creating the next artifact in the workflow, keeping your change progress on track without manual rework.

Core Features & Use Cases

  • Create and append the next artifact for an OpenSpec change to advance the workflow.
  • Validate and respect artifact order, statuses, and dependencies to ensure consistent progress.
  • Integrate with the OpenSpec CLI to generate artifacts, write them to the specified paths, and unlock subsequent steps.

Quick Start

Create the next artifact for your OpenSpec change by running the continue-change 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 create the next artifact for an OpenSpec change?

To create the next artifact for an OpenSpec change, you can automate the workflow by running the continue-change process. This automatically locates your current change, assesses its status, and generates the next required artifact to keep progress on track.

How does artifact generation work in OpenSpec change management?

Artifact generation in OpenSpec change management works by validating artifact order, statuses, and dependencies. It integrates with the OpenSpec CLI to locate the current change and automatically write the next artifact to specified paths to unlock subsequent workflow steps.

Do I need the OpenSpec CLI to continue a change workflow?

Yes, you need the OpenSpec CLI installed to continue a change workflow. The automation relies on the CLI to locate the current project context, assess the change status, and generate the next artifact in the specified paths.

Can I automate artifact creation for OpenSpec changes across multiple files?

Yes, you can automate artifact creation for OpenSpec changes across multiple artifacts. The workflow validates dependencies and statuses to ensure consistent progress, automatically generating and appending the next artifact to advance the workflow without manual rework.

What is the best way to maintain progress on an OpenSpec change?

The best way to maintain progress on an OpenSpec change is to automate continuing the workflow. By validating artifact order and dependencies, the process generates the next artifact automatically, ensuring consistent progress and preventing manual rework.

Why does my OpenSpec change workflow not advance to the next artifact?

An OpenSpec change workflow may not advance if artifact dependencies or statuses are not properly validated. The automation requires proper project context and the OpenSpec CLI to locate the current change and write the next artifact correctly.