openspec-continue-change

Generate the next OpenSpec artifact for a selected change.

6|1|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/ilaziness/vexo --skill openspec-continue-change-ilaziness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/ilaziness/vexo/tree/main/.crush/skills/openspec-continue-change
Command: npx skills add https://github.com/ilaziness/vexo --skill openspec-continue-change-ilaziness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you’re working through an OpenSpec change, you need a reliable way to continue from where you left off and generate the next deliverable in the correct order.

Core Features & Use Cases

  • List and select the change to continue: If no change name is provided, the skill helps you choose from the most recently modified changes without guessing.
  • Create the correct next artifact: It checks current status, picks the first artifact marked ready, and generates it using the provided template and instructions.
  • Stay in sync with progress: After writing the artifact, it reports unlocked progress and prompts you to continue.

Quick Start

Ask it to continue your OpenSpec change by providing the change name (or let it ask you to select one from your recent changes).

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 a spec-driven development workflow and generate the next artifact?

To continue an OpenSpec change, the system lists recently modified changes, checks artifact status, and generates the first ready artifact using CLI-provided templates and outputPath instructions. It then reports unlocked progress and prompts you to continue.

What is the process for resuming an OpenSpec change from where I left off?

Resuming an OpenSpec change involves listing recent modifications, selecting a change if one is not provided, and writing the first artifact marked ready to the CLI outputPath. This ensures you generate deliverables in the correct order without guessing.

How does artifact generation handle dependencies and guardrails in spec-driven development?

Artifact generation in spec-driven development respects templates, dependencies, and guardrails by retrieving specific artifact instructions from the CLI and writing the output to the provided path. It ensures deliverables transition correctly through ready, done, or blocked states.

Do I need to manually select a change name to continue an OpenSpec workflow?

You do not need to manually provide a change name to continue an OpenSpec workflow. If no change name is specified, the system helps you choose from the most recently modified changes using CLI commands to list available options.

What should I do if my OpenSpec artifact status is blocked during workflow continuation?

If your OpenSpec artifact status is blocked during workflow continuation, the system skips it and looks for the first artifact marked ready to generate. Deliverables must transition through ready states to be written to the CLI-provided outputPath.

Can I use CLI automation to track artifact progress in spec-driven development?

You can use CLI automation to track artifact progress in spec-driven development. After writing the next output to the outputPath, the system reports unlocked progress and prompts you to continue, keeping you in sync with the change timeline.