openspec-continue-change

Generate the next OpenSpec artifact for a change using the openspec CLI.

1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/durandom/layton --skill openspec-continue-change-durandom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/durandom/layton/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/durandom/layton --skill openspec-continue-change-durandom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact.

Core Features & Use Cases

  • Create the next artifact for the selected OpenSpec change to advance the workflow.
  • Check current status, fetch instructions, and apply dependencies to generate the artifact in the proper location.
  • Prompt for a specific change name if context is ambiguous and let the user choose instead of auto-selecting.

Quick Start

Specify the change name to continue, or allow inference from context so I 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 generate the next artifact for an OpenSpec change?

To generate the next OpenSpec artifact, the Skill queries the status and instructions endpoints to determine the required artifact, fetches its template, applies dependencies, and writes the output to the correct path to advance your workflow.

What is the OpenSpec change workflow process?

The OpenSpec change workflow progresses sequentially through proposal, specs, design, and tasks artifacts, using the CLI to track status and determine the next required document to generate and write to your project.

Do I need the openspec CLI to advance a change workflow?

Yes, the openspec CLI is required to advance a change workflow, as the Skill relies on its status and instructions endpoints to determine the next artifact and fetch the necessary templates and dependencies.

How do I specify which OpenSpec change to continue?

You can specify the change name directly to continue, or allow the Skill to infer the context, which will prompt you to choose the correct change if the context is ambiguous instead of auto-selecting.

Why is my OpenSpec change not advancing to the next artifact?

An OpenSpec change may not advance if the context is ambiguous and no specific change name is provided, preventing the Skill from auto-selecting the correct workflow to generate the next artifact.