openspec-apply-change

Implements tasks from an OpenSpec change with progress tracking and preflight validation.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill openspec-apply-change-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Wizarck/nexandro/tree/main/skills/openspec-apply-change
Command: npx skills add https://github.com/Wizarck/nexandro --skill openspec-apply-change-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved OpenSpec change proposal into working code is error-prone: tasks get skipped, cited identifiers drift on main, and progress tracking is manual. This Skill orchestrates the implementation loop so each task in the change is executed, checked off, and verified against the current codebase. ## Core Features & Use Cases - Change selection and status parsing: Resolves the target change from context or openspec list --json, then reads schema, progress, and task state via openspec status and openspec instructions apply. - Preflight citation drift check: Re-greps identifiers cited in proposal, design, and tasks files against main to detect renamed classes, migration slots, or ADR numbers before writing code. - Task-by-task implementation loop: Works through pending tasks, marks - [ ] to - [x] after each completion, and pauses with structured options on ambiguity, errors, or design issues. - Use Case: A developer has an approved OpenSpec change with 7 tasks. They invoke the Skill, which writes the apply-session marker, verifies cited identifiers still exist on main, implements each task, and reports 7/7 completion ready for archive. ## Quick Start Ask the AI to start implementing the tasks from your OpenSpec change, optionally naming the change to apply.

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 tasks from an OpenSpec change?▼

Invoke the apply workflow with an optional change name. The Skill runs openspec status and openspec instructions apply to load context files and the task list, then implements each pending task and marks its checkbox complete.

What happens if I don't specify a change name?▼

The Skill infers the change from conversation context, auto-selects when only one active change exists, or runs openspec list --json and asks you to pick when multiple changes are available.

Does the apply workflow detect stale identifiers in proposals?▼

Yes. A preflight step re-greps every file path, class name, migration slot, and ADR number cited in proposal, design, and tasks files against main. Drift of three or more identifiers blocks progress unless explicitly overridden.

What is the apply-session start marker for?▼

The marker, written via openspec_apply_marker.py, signals that the session is skill-orchestrated. A PreToolUse hook blocks the first edit on a slice's write paths unless this marker exists, enforcing the apply workflow.

What happens when implementation hits an error or unclear task?▼

The Skill pauses instead of guessing. It shows completed progress, describes the issue, and presents numbered options so you can choose how to proceed before any further changes are made.