openspec-continue-change

Validate OpenSpec change status and create the next workflow artifact.

2|1|Updated Mar 16, 2026

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

Ready to run

npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-continue-change-yi-ming-zhao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Yi-ming-Zhao/Fittin/tree/main/.cursor/skills/openspec-continue-change
Command: npx skills add https://github.com/Yi-ming-Zhao/Fittin --skill openspec-continue-change-yi-ming-zhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users to advance an OpenSpec change by producing the next artifact in the workflow, ensuring continuity and proper sequencing.

Core Features & Use Cases

Guided artifact creation: prompts for the next artifact in a change and uses the CLI to fetch status and instructions.
Status-driven workflow: validates progress, reads dependencies, and unlocks subsequent steps after artifact creation.
Safe, ordered execution: enforces the artifact sequence to prevent out-of-order work and maintain traceability.

Quick Start

Continue the current 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 create the next artifact in an OpenSpec change workflow?▼

To create the next artifact in an OpenSpec change workflow, you need a tool that validates the current status using openspec status, fetches necessary instructions, and writes the new artifact to the specified output path. This enforces the artifact sequence to prevent out-of-order work and maintain traceability.

How does OpenSpec change management enforce artifact sequencing?▼

OpenSpec change management enforces artifact sequencing by validating current progress and reading dependencies before unlocking subsequent steps. This safe, ordered execution prevents out-of-order work and maintains traceability throughout the workflow.

What is the best way to automate OpenSpec artifact progression?▼

The best way to automate OpenSpec artifact progression is using a status-driven workflow that validates progress, reads dependencies, and applies CLI instructions to write new artifacts. This ensures guided artifact creation and proper sequencing.

Do I need the openspec CLI to continue a change with the next artifact?▼

Yes, you need the openspec CLI to continue a change. The workflow uses the CLI to fetch the current status and necessary instructions, ensuring the new artifact is created safely and in the correct order.

Why does my OpenSpec change workflow have pending artifacts?▼

Your OpenSpec change workflow has pending artifacts because it enforces a safe, ordered execution sequence. It validates progress and reads dependencies before unlocking subsequent steps, preventing out-of-order work until the current status is confirmed.