openspec-apply-change

Executes OpenSpec change workflows using CLI commands and task checkboxes.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-apply-change-breuerfelix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/breuerfelix/spurwechsel/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-apply-change-breuerfelix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the effort of translating an OpenSpec change description into concrete, step-by-step implementation work across the correct artifacts, while keeping progress and status aligned.

Core Features & Use Cases

  • Select the right change reliably: Infers from context, auto-selects when unambiguous, and otherwise prompts for available OpenSpec changes via openspec list --json.
  • Fetch schema-aware instructions and context: Uses openspec instructions apply to detect the workflow schema and identify the correct contextFiles to read before coding.
  • Execute tasks with safe progress tracking: Iterates pending tasks, keeps changes minimal per task, marks each checkbox as complete, and pauses on blockers or ambiguity rather than guessing.

Quick Start

Tell the assistant: "Apply my OpenSpec change and implement all tasks using the provided context, then report progress and any blockers."

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 workflows step by step?

Implement OpenSpec change workflows by selecting the correct change, fetching schema-aware instructions via the openspec CLI, and executing tasks while reading the provided context files. Progress is tracked by updating task checkboxes immediately after each task is completed.

What is the best way to track code changes and task progress in schema-driven workflows?

Track task progress in schema-driven workflows by executing pending tasks iteratively and marking each checkbox complete immediately. The workflow pauses on blockers or ambiguity rather than guessing, ensuring safe progress tracking and minimal changes per task.

Can I resume partially completed OpenSpec implementations without losing my progress?

Yes, you can resume partially completed OpenSpec implementations. The workflow retrieves schema-aware instructions and context files to continue working through pending tasks, maintaining your existing progress by updating task checkboxes as each step is finished.

Do I need the openspec CLI to apply schema-driven implementation instructions?

Yes, the openspec CLI is required. The workflow depends on invoking openspec commands like list, status, and instructions apply to detect the schema, identify context files, and execute the listed implementation tasks correctly.

How does schema-aware task orchestration handle blocked or all_done states during code changes?

Schema-aware task orchestration handles blocked or all_done states by pausing execution and reporting the blocker rather than guessing. This prevents incorrect code changes and ensures implementation only proceeds when tasks are unambiguously ready.