openspec-continue-change

Create the next OpenSpec change artifact from CLI status and dependencies.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-continue-change-wtg42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/wtg42/tty-clock-timer/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-continue-change-wtg42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of progressing an OpenSpec change by automating the selection, status inspection, and creation of the next required artifact so the user doesn't need to manually read CLI JSON, track dependencies, or guess the next step.

Core Features & Use Cases

  • Guided change selection: Lists recent changes and prompts the user to choose which change to continue instead of guessing.
  • Status-driven artifact creation: Reads change status, fetches instructions for the next ready artifact, reads dependencies, and writes the artifact following schema rules.
  • Use Case: Perfect for product managers or engineers who want to incrementally produce proposal, spec, design, or tasks artifacts for an OpenSpec change without losing context or violating workflow order.

Quick Start

Continue the OpenSpec change "my-change" and create the next artifact by asking me to continue that change.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema
How do I advance an OpenSpec change to its next artifact without manually tracking dependencies?

OpenSpec change advancement automates status inspection and dependency reading to generate the next required artifact in the correct workflow order. The Skill lists recent changes, fetches instructions, and writes a single artifact per invocation.

What is the best way to create the next spec or proposal artifact for an OpenSpec change?

Creating the next artifact for an OpenSpec change requires parsing JSON status from the CLI, reading completed dependencies, and authoring the file in a spec-driven schema. This Skill automates that entire process to prevent workflow order violations.

Does OpenSpec workflow artifact creation require the openspec CLI to function?

Yes, OpenSpec artifact creation requires the openspec CLI to list changes, inspect change status, and fetch artifact instructions. The Skill parses JSON output from the CLI to determine which artifact to author next.

Can I use custom schemas when authoring OpenSpec change artifacts?

OpenSpec artifact authoring supports both spec-driven and custom schemas. The Skill fetches instructions for the next ready artifact and writes it to the specified output path following the schema rules provided.

Why does my OpenSpec change workflow not progress to the design or tasks artifact?

OpenSpec change progression stops when dependencies are incomplete or the workflow order is violated. This Skill reads change status and completed dependencies to ensure the next artifact is only created when its prerequisites are met.

How do I select which OpenSpec change to continue when multiple changes exist?

Selecting an OpenSpec change to continue is guided by listing recent changes and prompting the user to choose. This prevents guessing and ensures the correct change status and dependencies are loaded before artifact creation.