openspec-apply-change

Implement OpenSpec change tasks with interactive progress tracking.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/twilwa/THE-REVENGER --skill openspec-apply-change-twilwa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/twilwa/THE-REVENGER/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/twilwa/THE-REVENGER --skill openspec-apply-change-twilwa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement tasks from an OpenSpec change.

Core Features & Use Cases

  • Guided change workflow: select a change, verify status, and fetch apply instructions.
  • Read and apply tasks incrementally: step through pending tasks, update task status, and handle blockers.
  • Dynamic context handling: read context files and adjust guidance based on schema states.

Quick Start

Provide the change name to start applying an OpenSpec change.

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 changes incrementally?

To implement OpenSpec changes incrementally, this skill interactively selects changes, validates status, and steps through pending tasks while reading relevant context files. It enforces deterministic task progression and updates task checkboxes as you progress.

What is state-aware task automation for schema-driven changes?

State-aware task automation for schema-driven changes is a workflow mechanism that dynamically reads context files and adjusts instructions based on schema states. It enforces deterministic task progression and prompts for ambiguous inputs during execution.

How do I track progress and update task status for OpenSpec changes?

You can track progress and update task status for OpenSpec changes by stepping through pending tasks and executing them sequentially. The workflow validates current status, handles blockers interactively, and updates task checkboxes automatically.

What's the best way to handle ambiguous inputs during change management workflows?

The best way to handle ambiguous inputs during change management workflows is to use interactive prompts that enforce deterministic task progression. This skill validates status and interactively requests clarification before proceeding with schema-driven changes.

Do I need to provide a change name to start applying an OpenSpec change?

Yes, you need to provide the change name to start applying an OpenSpec change. Once provided, the workflow fetches apply instructions, verifies status, and dynamically reads context files to guide incremental task execution.

Why does context reading matter for incremental task execution?

Context reading matters for incremental task execution because it allows the workflow to dynamically adjust guidance based on schema states. By reading relevant context files, the system enforces deterministic progression and prevents invalid task updates.