openspec-apply-change

Execute OpenSpec change tasks with status and instruction context.

22|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/izzoa/polyrouter --skill openspec-apply-change-izzoa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/izzoa/polyrouter/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/izzoa/polyrouter --skill openspec-apply-change-izzoa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you carry an OpenSpec change from planning to implementation by identifying the active change, loading the right task context, and guiding you through the remaining work safely and in order.

Core Features & Use Cases

  • Change selection: Picks or disambiguates the correct OpenSpec change when multiple options exist.
  • Status and context loading: Reads the change status and instructions so implementation matches the active schema and artifacts.
  • Task-by-task execution: Works through pending tasks, updates checkboxes as each one is completed, and pauses when requirements are unclear or blocked.
  • Use case: A developer asks to continue an in-progress OpenSpec change, and this Skill guides them through the exact tasks needed to finish it.

Quick Start

Use the openspec-apply-change skill to continue the active change and complete the next pending task.

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 spec-driven changes task by task?

Spec-driven development implementation requires reading change status and instructions, then executing tasks sequentially. This Skill selects the active OpenSpec change, loads artifact context, and tracks task-by-task progress while pausing for ambiguity or blockers.

What is OpenSpec change management for development workflows?

OpenSpec change management is a spec-driven workflow tracking implementation progress task by task. It uses a CLI to select active changes, load apply instructions, validate schemas, and update completion status for structured development.

Do I need the openspec CLI to execute change tasks?

Yes, executing change tasks requires the openspec CLI. The Skill relies on change-scoped CLI commands to read status, load instructions, list changes, run validation, and update task completion checkboxes.

How do I continue an in-progress OpenSpec change?

Continuing an in-progress OpenSpec change involves selecting the active change, disambiguating if multiple exist, reading current status, and executing the next pending task. The Skill loads artifact context and matches the active schema automatically.

What happens when requirements are unclear during change implementation?

When requirements are unclear during change implementation, the Skill pauses execution to prevent errors. It stops task-by-task progress upon detecting blockers or ambiguity, ensuring implementation proceeds only when the path is clear.

How does task execution handle multiple active OpenSpec changes?

When multiple active OpenSpec changes exist, task execution performs change selection and disambiguation. It identifies the correct change context, loads specific status and instructions, and ensures implementation targets only the intended change.