openspec-continue-change

Create the next required OpenSpec artifact based on current change status.

30|1|Updated Feb 18, 2026

Search Tags:#task management #development workflow #openspec #spec management #artifact generation

Ready to run

npx skills add https://github.com/pacaplan/flokay --skill openspec-continue-change-pacaplan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the development workflow by allowing users to seamlessly continue working on their OpenSpec changes, ensuring progress through the creation of necessary artifacts.

Core Features & Use Cases

Progressive Artifact Creation: Guides users through creating the next required artifact for an OpenSpec change, whether it's a proposal, spec, design, or task list.
Contextual Awareness: Automatically infers or prompts for the specific change to work on, leveraging conversation history and openspec list output.
Use Case: After defining a new feature's proposal, use this Skill to automatically generate the corresponding specification file based on the defined capabilities.

Quick Start

Use the openspec-continue-change skill to create the next artifact for your current development 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 continue an OpenSpec development workflow and generate the next artifact?▼

To continue an OpenSpec workflow, this Skill programmatically identifies the current change status and generates the next required artifact, such as a proposal, spec, design, or task list. It leverages schema-driven processes to ensure sequential progress.

What is the best way to automatically create specification files after defining an OpenSpec proposal?▼

Automatically creating specification files from an OpenSpec proposal is handled by checking the change status via the OpenSpec CLI. The Skill then retrieves artifact instructions to generate the corresponding specification based on your defined capabilities.

Do I need the OpenSpec CLI installed to manage artifact generation for my changes?▼

Yes, the OpenSpec CLI is required to manage artifact generation. The Skill depends on the CLI to perform status checks and retrieve the necessary artifact instructions for your current development changes.

Can I use conversation history to specify which OpenSpec change to work on?▼

Yes, you can use conversation history to specify the OpenSpec change. The Skill features contextual awareness that automatically infers the specific change to work on, or it will prompt you based on the `openspec list` output.

What types of artifacts can I generate when advancing my spec management workflow?▼

When advancing your spec management workflow, you can generate progressive artifacts including proposals, specifications, designs, and task lists. The Skill guides you through creating the exact next artifact required by the schema-driven process.

Why does my OpenSpec change workflow stop progressing after creating a proposal?▼

An OpenSpec change workflow stops progressing if the next sequential artifact is missing. This Skill resolves the stall by querying the current status and programmatically creating the next required specification, design, or task list.