skills.rest
arestivo
arestivoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-continue-change

Generate the next OpenSpec change artifact from CLI status and instructions.

Updated Feb 5, 2026
Search Tags:#automation#workflow#CLI#openspec#artifact#change-management
One-click install
npx skills add https://github.com/arestivo/qoodle --skill openspec-continue-change-arestivo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/arestivo/qoodle/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/arestivo/qoodle --skill openspec-continue-change-arestivo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers progress an OpenSpec change by automatically creating the next artifact in the change workflow, ensuring continuity and traceability.

Core Features & Use Cases

  • Automated artifact progression: Generates the next artifact in the OpenSpec workflow based on the current state.
  • Status-driven guidance: Reads openspec status and instructions to identify the next actionable artifact.
  • CLI-driven workflow: Integrates with the openspec CLI to manage changes without manual scaffolding.

Quick Start

Open a terminal and run the following in sequence:

  • Check progress: openspec status --change "<name>" --json
  • If artifacts are ready, fetch instructions: openspec instructions <artifact-id> --change "<name>" --json
  • Create the artifact file using the provided template and save it to the path indicated in the instructions
  • Re-check progress: openspec status --change "<name>"

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate creating the next artifact in an OpenSpec change workflow?▼

OpenSpec artifact creation is automated by reading the openspec CLI status and instructions, then generating the subsequent artifact file based on the current workflow state. This ensures continuity and traceability without manual scaffolding.

How does the OpenSpec CLI status command guide artifact progression?▼

The OpenSpec CLI status command outputs the current change state in JSON, identifying the next actionable artifact. It drives progression by indicating which instructions to fetch for creating the required workflow file.

What is the process to advance an OpenSpec change using the CLI?▼

Advancing an OpenSpec change involves running openspec status, fetching artifact instructions, creating the file from the template, and re-checking status. This sequential CLI process advances the change workflow.

Do I need any external dependencies to manage OpenSpec artifacts via the CLI?▼

No external dependencies are required to manage OpenSpec artifacts. The workflow relies entirely on the openspec CLI to interpret status, fetch instructions, and generate artifact files in the correct order without additional packages.

Why is my OpenSpec change not progressing to the next artifact?▼

An OpenSpec change stalls when the status output indicates incomplete prerequisites or if the artifact file is not saved to the exact path in the fetched instructions. Re-check the JSON status output for errors.

Related Skills

Explore More Software Engineering Skills→
optionioptioni

openspec-new-change

Automate initiation of a new OpenSpec change with structured user interaction.

Official
Intermediate
rock-hurock-hu

openspec-archive-change

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Community
Advanced
soyrochussoyrochus

openspec-continue-change

Continue OpenSpec change workflows by parsing status and creating the next artifact file.

Community
Intermediate
brandon-setegnbrandon-setegn

openspec-ff-change

Create OpenSpec change artifacts from a change name or feature description.

Community
Intermediate