openspec-continue-change

Create the next artifact in an OpenSpec change sequence.

Updated Dec 8, 2025
One-click install
npx skills add https://github.com/open-platform-model/cli --skill openspec-continue-change-open-platform-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/open-platform-model/cli/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/open-platform-model/cli --skill openspec-continue-change-open-platform-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams advance an OpenSpec change by generating the next artifact required to continue the workflow, reducing wait times and ensuring consistent progression.

Core Features & Use Cases

  • Automatically selects and creates the next artifact in the OpenSpec change sequence based on the current status.
  • Guides users through continuing complex changes by enforcing artifact order and leveraging dependency context.
  • Use Case: A developer is midway through an OpenSpec change; this Skill creates the next artifact to move the change forward and unlock subsequent steps.

Quick Start

Create the next artifact for the selected OpenSpec change and guide the user through the continuation workflow.

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 change and generate the next artifact?

To continue an OpenSpec change, you can automate the generation of the next artifact. The workflow reads existing dependencies, enforces artifact order, and writes the new artifact to the specified path.

How does artifact order enforcement work in an OpenSpec workflow?

Artifact order enforcement ensures sequential progression by reading dependencies and current status. It prevents out-of-sequence artifact creation, maintaining consistent workflow advancement.

Can I use this automation to advance an OpenSpec change midway through development?

Yes, this automation applies when a developer is midway through an OpenSpec change. It creates the next required artifact to move the change forward and unlock subsequent development steps.

What is the best way to add the next artifact to an existing OpenSpec change?

The best way to add the next artifact is to automate the continuation process. This ensures the new artifact respects existing context and rules while being written to the correct specified path.

Why does my OpenSpec workflow stall when trying to progress a change?

An OpenSpec workflow may stall if the required artifact sequence is incomplete. Automating the continuation enforces artifact order and generates the next required artifact to unlock subsequent steps.