openspec-continue-change

Generate the next OpenSpec change artifact via the CLI workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yuanhsunliu/dashboard-layout-editor-ui --skill openspec-continue-change-yuanhsunliu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/yuanhsunliu/dashboard-layout-editor-ui/tree/main/.github/skills/openspec-continue-change
Command: npx skills add https://github.com/yuanhsunliu/dashboard-layout-editor-ui --skill openspec-continue-change-yuanhsunliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Guided continuation: prompts to select the change when multiple are available and ensures you continue in the correct sequence.
  • Status-driven creation: checks current artifact readiness and creates the next artifact in order.
  • Guardrails & dependencies: reads completed artifacts to inform the next steps and enforces ordering.

Quick Start

Prompt the user to pick a change, then run openspec status to determine the next artifact and execute openspec instructions for that 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 in sequence?

To continue an OpenSpec change, you select the change and run the CLI status check to determine the next artifact. The workflow then executes instructions to generate that artifact in the correct sequential order.

What is the OpenSpec workflow for checking artifact readiness before creation?

The OpenSpec workflow checks artifact readiness by reading completed dependency artifacts and enforcing ordering guardrails. It verifies current status before generating the next artifact in the sequence.

How do I handle multiple OpenSpec changes when continuing a workflow?

When multiple OpenSpec changes exist, the workflow prompts you to select the specific change you want to continue. This ensures you progress the correct sequence and generate artifacts for the intended change.

Does the OpenSpec CLI enforce dependency ordering when generating artifacts?

Yes, the OpenSpec CLI enforces dependency ordering by reading completed artifacts to inform next steps. It applies guardrails that ensure artifacts are created in the correct sequence.

Can I use the OpenSpec continue-change workflow for iterative spec-driven development?

Yes, the OpenSpec continue-change workflow is designed for iterative spec-driven development. It automates progressing changes by checking status and creating the next artifact in sequence across multiple iterations.