openspec-continue-change

Generate the next OpenSpec change artifact from completed dependencies.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/YangYuS8/blog --skill openspec-continue-change-yangyus8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/YangYuS8/blog/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/YangYuS8/blog --skill openspec-continue-change-yangyus8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the continuation of OpenSpec changes by generating the next artifact to keep the workflow moving.

Core Features & Use Cases

  • Orchestrates the next artifact creation within an OpenSpec change, including change selection, status checks, and artifact generation.
  • Handles multiple workflow schemas and reads dependencies from completed artifacts to populate context.
  • Guides users through a deterministic, guard-railed process that ensures prerequisites are satisfied before creation.

Quick Start

Ask for the change name and instruct me to continue by generating the next OpenSpec 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 automate the next artifact generation in an OpenSpec change workflow?

Automating OpenSpec artifact generation requires providing the change name so the workflow can check status, read dependencies from completed artifacts, and produce the next output deterministically.

What is template-driven artifact creation in change management workflows?

Template-driven artifact creation uses predefined schemas and dependency reading to guide generating the next artifact in a change management workflow, ensuring all prerequisites are satisfied before creating the output.

Can I continue an OpenSpec workflow across multiple schemas?

Yes, the OpenSpec continuation workflow handles multiple workflow schemas by reading dependencies from completed artifacts to populate context and safely advance to the next artifact creation step.

How do I ensure prerequisites are satisfied before generating the next OpenSpec artifact?

Ensuring prerequisites are satisfied involves applying guard-railed checks that validate change status and completed dependencies before allowing the next artifact generation to proceed deterministically.

What are the limitations of automated OpenSpec change continuation?

Automated OpenSpec change continuation relies on deterministic, guard-railed processes, meaning it requires existing completed artifacts for dependency reading and cannot generate outputs if prerequisite status checks fail.