openspec-continue-change

Create the next OpenSpec change artifact in schema-defined order.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-continue-change-maplumex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/MaplumeX/Blockwise/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-continue-change-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact.

Core Features & Use Cases

  • Guides you through selecting the current change, checking status, and determining the next artifact to create.
  • Enforces artifact order and uses the schema-specific instructions to generate the correct artifact structure.
  • Supports dependency awareness by reading completed artifacts before writing the new one.

Quick Start

Tell Openspec to continue the change and generate the next 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 continue an OpenSpec change and generate the next artifact?

To continue an OpenSpec change, specify or infer the change name to read its current status, select the next ready artifact, and write it using schema instructions and templates. This ensures artifacts are created in proper order.

How does artifact ordering work in an OpenSpec change workflow?

Artifact ordering in an OpenSpec change workflow enforces sequential creation by reading the change status, determining the next ready artifact, and applying dependency awareness by reading completed artifacts before writing the new one.

Do I need to manually select the next artifact when progressing an OpenSpec change?

No, you do not need to manually select the next artifact. The workflow automatically determines the next ready artifact by reading the current change status and enforcing artifact order based on completed dependencies.

What is the best way to manage dependencies between artifacts in an OpenSpec change?

Managing dependencies between artifacts in an OpenSpec change is handled by reading completed artifacts before writing the new one. This dependency awareness ensures the generated artifact structure aligns with prior outputs.

Can I use schema-specific templates to structure artifacts in a change management workflow?

Yes, you can use schema-specific templates to structure artifacts in a change management workflow. The process enforces artifact order and applies schema-specific instructions to generate the correct artifact structure.

Why does my OpenSpec change workflow stop before creating the next artifact?

An OpenSpec change workflow stops before creating the next artifact if the status indicates incomplete dependencies or if the next artifact is not ready. It reads the status and selects the next ready artifact only when constraints are met.