openspec-continue-change

Create the next required OpenSpec change artifact using the OpenSpec CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users continue their work on an OpenSpec change by creating the next required artifact in the workflow, ensuring a smooth progression from proposal to implementation.

Core Features & Use Cases

  • Artifact Generation: Automatically creates the next artifact (e.g., spec, design, tasks) based on the current status of an OpenSpec change.
  • Workflow Management: Guides the user through the OpenSpec process by identifying and creating artifacts in the correct sequence.
  • Use Case: After creating a proposal for a new feature, use this Skill to automatically generate the corresponding specification file, then later to create the design document, and finally the implementation tasks.

Quick Start

Use the openspec continue change skill to create the next artifact for the 'user-auth' 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 generate the next artifact in an OpenSpec change workflow?

This Skill generates the next artifact in an OpenSpec change workflow by checking the current status via the CLI and programmatically creating the required specification, design, or tasks file based on predefined schemas.

What is the correct sequence for OpenSpec artifact generation during development?

The correct sequence for OpenSpec artifact generation progresses from proposal to specification, then to design, and finally to implementation tasks. This Skill identifies your current workflow status and creates the next required artifact automatically.

Do I need the OpenSpec CLI to manage change status and artifact creation?

You need the OpenSpec CLI to manage change status and artifact creation. This Skill requires the CLI to retrieve workflow instructions, check current status, and list artifacts before programmatically generating the next file.

Can I automate specification file creation after submitting an OpenSpec proposal?

You can automate specification file creation after an OpenSpec proposal. This Skill identifies the proposal status and programmatically generates the corresponding specification file using predefined schemas to ensure smooth workflow progression.

How does change management workflow sequencing work with OpenSpec?

Change management workflow sequencing with OpenSpec requires creating artifacts in a specific order. This Skill manages the sequence by checking the change status and generating the next missing spec, design, or tasks document.

What are the limitations of automating OpenSpec artifact generation?

A limitation of automating OpenSpec artifact generation is the strict dependency on the OpenSpec CLI for status checking and instructions. It cannot generate artifacts out of sequence or bypass predefined schema requirements.