openspec-continue-change

Create the next OpenSpec change artifact based on workflow status.

2|Updated Feb 19, 2026

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

Ready to run

npx skills add https://github.com/llama-farm/demofly-claude --skill openspec-continue-change-llama-farm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/llama-farm/demofly-claude/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/llama-farm/demofly-claude --skill openspec-continue-change-llama-farm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to keep an OpenSpec change moving by automatically generating the next artifact required to progress a change through its lifecycle.

Core Features & Use Cases

Creates the next artifact for an OpenSpec change when the user wants to advance their workflow.
Prompts for the change name if ambiguous, inspects status, and reads dependencies to determine what to produce next.
Handles multiple status scenarios (complete, ready to create, blocked) and documents the resulting artifact and unlocks.

Quick Start

Continue an OpenSpec change by creating 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 skill inspects the change status, reads dependencies, and writes the new artifact according to the schema template to progress the workflow.

What happens if my OpenSpec change name is ambiguous when creating artifacts?▼

When the OpenSpec change name is ambiguous, the skill prompts you to specify the correct change name before checking its status and generating the next artifact.

How does OpenSpec handle change status states like complete, ready, or blocked?▼

OpenSpec handles complete, ready, and blocked status states by evaluating dependencies to determine if an artifact can be created or if the change workflow is blocked.

Do I need any external dependencies to automate OpenSpec change management?▼

No external dependencies are required to automate OpenSpec change management, as the skill operates independently to inspect status and create workflow artifacts.

What is the best way to progress a blocked OpenSpec change workflow?▼

To progress a blocked OpenSpec change workflow, the skill reads dependencies and reports the status, identifying what is needed to unblock and create the next artifact.

Why does OpenSpec check dependencies before writing a new change artifact?▼

OpenSpec checks dependencies before writing a new artifact to ensure the change status is ready, preventing artifact generation when the workflow is blocked or already complete.