openspec-continue-change

Create the next required OpenSpec artifact and advance change workflow via CLI.

Updated Apr 11, 2025
One-click install
npx skills add https://github.com/pabloimrik17/monolab --skill openspec-continue-change-pabloimrik17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/pabloimrik17/monolab/tree/main/.junie/skills/openspec-continue-change
Command: npx skills add https://github.com/pabloimrik17/monolab --skill openspec-continue-change-pabloimrik17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users progress an OpenSpec-managed change by identifying the next artifact to produce, generating that artifact from CLI-provided templates and instructions, and updating change progress so the workflow continues without guesswork.

Core Features & Use Cases

  • Guided change selection: Lists recent changes and prompts the user to choose which change to continue when the change name is not provided or ambiguous.
  • Status-aware artifact creation: Queries change status, selects the first ready artifact, fetches artifact instructions, reads completed dependencies for context, and writes the new artifact file.
  • Safe, single-step progress: Creates exactly one artifact per invocation, validates progress afterward, and informs the user what unlocked next steps.
  • Use Case: A developer wants to continue a design change started earlier; the Skill picks up the selected change, creates the next spec or design artifact, and shows updated progress.

Quick Start

Ask me to continue a change or provide the change name so I can fetch status, get instructions, and 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 continue an OpenSpec change and create the next artifact?

The Skill selects a ready OpenSpec change, queries its status, fetches artifact instructions via the openspec CLI, reads completed dependencies, and writes exactly one new artifact file to advance the workflow.

What is spec-driven change management and how does it work with OpenSpec?

Spec-driven change management uses the openspec CLI to track change status and generate required artifacts sequentially. The Skill automates this by fetching templates and writing the next artifact based on completed dependency context.

Do I need the openspec CLI installed to generate change artifacts?

Yes, the openspec CLI must be available in your environment. The Skill relies on CLI commands returning JSON data to list changes, check status, and obtain the artifact instructions needed for creation.

Can I create multiple spec artifacts at once for a single OpenSpec change?

No, the Skill creates exactly one artifact per invocation to ensure safe, single-step progress. After writing the artifact, it validates progress and informs you of the unlocked next steps.

How does the Skill handle ambiguous OpenSpec change selection?

When a change name is missing or ambiguous, the Skill lists recent changes and prompts the user to choose. It requires explicit user confirmation before proceeding with artifact creation.

Why does my OpenSpec workflow automation stop after creating one artifact?

The workflow pauses because the Skill creates exactly one artifact per invocation for safe, single-step progress. You must invoke it again to fetch instructions and generate the next unlocked artifact.