skills.rest
martinsson
martinssonCOMMUNITY
Explore all skills by this author →
GitHub

openspec-continue-change

Create the next OpenSpec artifact in sequence from change status and CLI data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This OpenSpec helper streamlines progressing a change through its artifact lifecycle by automating the creation of the next artifact in the sequence.

Core Features & Use Cases

  • Change-selection workflow: prompts for a change name if not provided and lists recent changes by modification date.
  • Status-driven artifact creation: checks current status and creates the next artifact only when ready, respecting artifact order.
  • Progress visibility: reports which artifact was created and what is unlocked next, guiding the user to continue.

Quick Start

Tell OpenSpec to continue on your selected change to generate 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 automate creating the next artifact in an OpenSpec change workflow?▼

To continue an OpenSpec change, the workflow prompts for a change name if omitted, lists recent changes by modification date, checks the current status, and generates the next artifact in the correct order.

What happens if I try to generate an OpenSpec artifact before the change is ready?▼

The workflow checks the current status and only creates the next artifact when ready, respecting artifact order and preventing premature generation until dependency artifacts are completed.

How does OpenSpec handle ambiguous change names when continuing a workflow?▼

When a change name is omitted or ambiguous, OpenSpec prompts for selection by listing recent changes sorted by modification date, ensuring you select the correct change before generating the next artifact.

Can I see what artifact is unlocked next after generating an OpenSpec change artifact?▼

After creating an artifact, OpenSpec reports which artifact was created and what is unlocked next, providing progress visibility that guides you to continue the change workflow through its lifecycle.

Does the OpenSpec change workflow require manual artifact schema input?▼

No manual schema input is required; the workflow fetches artifact instructions automatically and writes the new artifact to the specified output path according to the schema guidance by querying the OpenSpec CLI.

Related Skills

Explore More Software Engineering Skills→
rafazafarrafazafar

openspec-continue-change

Generate the next OpenSpec artifact in the approved sequence.

Community
Advanced
hossam7amdyhossam7amdy

openspec-continue-change

Generates the next OpenSpec artifact from CLI status and dependency context.

Community
Advanced
SiddharthChillaleSiddharthChillale

openspec-new-change

Scaffold OpenSpec changes with kebab-case names and first artifact templates.

Community
Intermediate
roger8broger8b

openspec-continue-change

Generate OpenSpec change artifacts to continue workflow progression.

Community
Intermediate