openspec-apply-change

Apply OpenSpec change instructions to implement planned tasks stepwise.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably implement the tasks described by an OpenSpec change, so you can move from plan to working implementation without guessing what to do next.

Core Features & Use Cases

  • Selects the right OpenSpec change: Infers from context, auto-selects when only one active change exists, or lets you choose via openspec list --json when ambiguous.
  • Understands schema and artifacts: Uses openspec status and parses the schema to find where tasks and context live.
  • Applies state-aware instructions: Runs openspec instructions apply and handles blocked, all-done, and in-progress states to guide implementation.
  • Implements tasks with guardrails: Reads all contextFiles first, works task-by-task, minimizes code changes, updates task checkboxes, and pauses for ambiguity or blockers.
  • Keeps progress transparent: Reports schema, session completion, remaining tasks, and what to do next if paused or finished.

Quick Start

Ask the assistant to apply a specific OpenSpec change by name, or let it infer the change from your conversation context.

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement OpenSpec change plans automatically?

To automate OpenSpec code changes, apply change instructions through the OpenSpec CLI to execute planned tasks. The workflow parses context files, implements tasks step-by-step, and updates progress until all tasks are done.

What is a schema-driven workflow for code changes?

A schema-driven workflow for code changes uses a defined schema to locate tasks and context files within your project. It guides implementation by parsing structured JSON from status checks to ensure code modifications align with the plan.

How do I continue an in-progress OpenSpec task?

To continue an in-progress OpenSpec task, run the apply instructions command to retrieve the current state. The workflow handles in-progress, blocked, or all-done states to guide subsequent implementation steps from where you left off.

Do I need the OpenSpec CLI to apply change instructions?

Yes, you need the OpenSpec CLI to apply change instructions because the workflow relies on its commands to run status checks, parse returned JSON for context files, and update task execution progress.

How does the workflow handle blocked tasks during implementation?

When tasks are blocked during implementation, the workflow pauses execution and reports the remaining tasks alongside what to do next. It minimizes code changes and stops to prevent incorrect modifications when ambiguity arises.

What is the best way to manage multiple active OpenSpec changes?

The best way to manage multiple active OpenSpec changes is to list them using the CLI JSON output. The workflow auto-selects a change if only one is active, or prompts you to choose when multiple changes exist.