openspec-continue-change

Generate the next OpenSpec workflow artifact from existing change dependencies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bgzbgz/show-time --skill openspec-continue-change-bgzbgz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/bgzbgz/show-time/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/bgzbgz/show-time --skill openspec-continue-change-bgzbgz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continues OpenSpec changes by automatically generating the next artifact in the workflow.

Core Features & Use Cases

  • Supports multi-step OpenSpec workflows (proposal, specs, design, tasks) by creating the next artifact in the sequence.
  • Prompts the user to select which change to continue when multiple are available and ensures proper sequencing.
  • Validates existing artifacts and dependencies, writes the new artifact to the correct path, and exposes progress.

Quick Start

Ask OpenSpec to continue a change by creating the next artifact.

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is OpenSpec change workflow automation?

To continue an OpenSpec change, prompt the workflow to generate the next artifact. The system selects the active change, enforces sequence integrity across proposal, specs, design, and tasks, and writes the new artifact to the specified path.

How do I create the next artifact in an OpenSpec change sequence?

To continue an OpenSpec change, prompt the workflow to generate the next artifact. The system selects the active change, enforces sequence integrity across proposal, specs, design, and tasks, and writes the new artifact to the specified path.

Can I select a specific OpenSpec change when multiple changes are active?

OpenSpec workflows enforce sequence integrity by validating existing artifacts and reading dependencies. It ensures the next artifact in the proposal, specs, design, or tasks sequence is only created when prior dependencies are met.

How does OpenSpec enforce sequence integrity for change artifacts?

OpenSpec workflows enforce sequence integrity by validating existing artifacts and reading dependencies. It ensures the next artifact in the proposal, specs, design, or tasks sequence is only created when prior dependencies are met.

What are the standard artifact stages in OpenSpec change management?

OpenSpec change management supports multi-step workflows including proposal, specs, design, and tasks stages. It is suited for CLI-driven automation workflows that require structured artifact generation and dependency validation.

Does OpenSpec workflow support CLI automation for change management?

OpenSpec change management supports multi-step workflows including proposal, specs, design, and tasks stages. It is suited for CLI-driven automation workflows that require structured artifact generation and dependency validation.