openspec-continue-change

Create the next OpenSpec change artifact using the openspec CLI.

1|Updated Feb 22, 2026

Search Tags:#workflow #spec-driven #cli #openspec #artifact #change-management

Ready to run

npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-continue-change-siddharthchillale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/SiddharthChillale/cloud-operations-reasoning-agent/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-continue-change-siddharthchillale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users continue an existing OpenSpec change by determining the next required artifact, following schema rules, and creating that artifact in-project so workflows progress without manual file assembly.

Core Features & Use Cases

Prompt the user to select a change when the target is ambiguous and list the most recently modified changes.
Inspect change status, retrieve artifact-specific instructions, read completed dependency artifacts for context, and create exactly one new artifact per invocation.
Use Case: A developer working with a spec-driven workflow can ask the assistant to continue a change to produce the next spec or design document while preserving project constraints.

Quick Start

Ask the assistant to continue the change and it will prompt you to select a change and create the next artifact using the openspec CLI.

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 change status via the openspec CLI, retrieves artifact-specific instructions, reads completed dependency artifacts for context, and writes exactly one new artifact per invocation to progress the spec-driven workflow.

What is a spec-driven workflow artifact and when do I need to create one?▼

A spec-driven workflow artifact is a project file like a spec or design document required by a schema. You need to create one when progressing an OpenSpec change to maintain project constraints without manual file assembly.

Do I need the openspec CLI installed to use this spec-driven change management workflow?▼

Yes, you need the openspec CLI installed and accessible. The Skill requires it to run list, status, and instructions commands, and needs permission to read and write project artifact files.

Can I use custom schemas for artifact creation in OpenSpec change management?▼

Yes, the Skill supports both spec-driven and custom schemas for artifact creation. It fetches artifact-specific instructions and enforces context and rules while writing the new artifact to your project.

Why does the OpenSpec change progression only create one artifact at a time?▼

Creating exactly one artifact per invocation ensures schema rules are followed and context is preserved. This prevents manual file assembly errors and maintains project constraints throughout the change management workflow.