openspec-continue-change

Automate sequential OpenSpec artifact creation for proposal, spec, design, and tasks.

1|Updated Mar 7, 2026

Search Tags:#workflow #schema #development process #change management #openspec #artifact generation

Ready to run

npx skills add https://github.com/charlestang/UnaEditor --skill openspec-continue-change-charlestang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/charlestang/UnaEditor/tree/main/.gemini/skills/openspec-continue-change
Command: npx skills add https://github.com/charlestang/UnaEditor --skill openspec-continue-change-charlestang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the development workflow for OpenSpec changes by automating the creation of subsequent artifacts, ensuring a consistent and guided progression through the defined process.

Core Features & Use Cases

Artifact Generation: Automatically creates the next required artifact (e.g., proposal, spec, design, tasks) based on the current state of an OpenSpec change.
Workflow Guidance: Enforces the correct sequence of artifacts according to the specified schema.
Use Case: After creating a proposal for a new feature using OpenSpec, you can use this Skill to automatically generate the corresponding specification file, ensuring all necessary details are captured before moving to design.

Quick Start

Use the openspec-continue-change skill to create the next artifact for the 'user-authentication' 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 automate OpenSpec artifact generation for a new change?▼

To automate OpenSpec artifact generation, use this Skill to automatically create the next required file, such as a specification or design, based on the current state of your change.

What is the correct sequence for OpenSpec proposal, specification, and design files?▼

The correct sequence for OpenSpec artifacts follows a defined workflow: proposal, specification, design, and then tasks, ensuring a guided progression through the development process.

How do I enforce schema-driven workflows when creating OpenSpec changes?▼

To enforce schema-driven workflows, this Skill guides users through defined processes and manages artifact dependencies, ensuring adherence to the specified schema during creation.

Can I automatically generate the next required artifact after creating an OpenSpec proposal?▼

Yes, you can automatically generate the next required artifact after creating an OpenSpec proposal, as the Skill evaluates the current change state and creates the subsequent specification file.

Why does my OpenSpec change workflow require sequential artifact generation?▼

Your OpenSpec change workflow requires sequential artifact generation to ensure a consistent progression and capture all necessary details before moving from specification to design.