openspec-continue-change

Create the next OpenSpec change artifact in workflow sequence.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-continue-change-yandiaan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/yandiaan/penginfo-handal-hackathon/tree/main/.qoder/skills/openspec-continue-change
Command: npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-continue-change-yandiaan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on a change by creating the next artifact.

Core Features & Use Cases

  • Continue the change workflow by generating the next artifact in sequence.
  • Check the status of the current change to determine what's ready to create.
  • Respect dependencies and artifact order so tasks are created in the correct order.

Quick Start

Ask me to continue the change, and I will create the next artifact following the current OpenSpec 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 workflow and generate the next artifact?

To continue an OpenSpec change, request to proceed and the system creates the next artifact in sequence by checking the current status, inferring the correct file, and applying guarded sequencing.

What is OpenSpec change management and how does artifact sequencing work?

OpenSpec change management automates workflow progression by generating the next artifact in a dependency-aware sequence, ensuring tasks are created in the correct order rather than randomly.

Do I need the OpenSpec CLI to create the next artifact in a change workflow?

Yes, you need the OpenSpec CLI installed and configured, as the artifact creation process relies on it to handle dependencies and enforce the correct artifact order.

Can I skip artifacts or create them out of order when managing an OpenSpec change?

No, artifact creation respects strict dependency handling and sequencing rules, meaning you cannot skip ahead and must generate the required artifact files in the correct workflow order.

How do I check the status of an ongoing OpenSpec change to see what artifact is ready?

You can check the status of an ongoing change by prompting the workflow to continue, which evaluates the current state and determines or infers the next artifact that is ready to be created.

What happens if artifact dependencies are not met when continuing an OpenSpec change?

If dependencies are not met, the guarded sequencing prevents the next artifact from being created, ensuring the workflow stops until prerequisite artifact files are properly generated.