openspec-apply-change

Implements pending tasks for a specified OpenSpec change via CLI-driven workflow.

17|6|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/gmf520/openspec-agents --skill openspec-apply-change-gmf520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/gmf520/openspec-agents/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/gmf520/openspec-agents --skill openspec-apply-change-gmf520

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

This Skill helps you implement the pending work for a specific OpenSpec change without losing alignment to the prescribed workflow, artifacts, and task progress.

Core Features & Use Cases

  • Selects and validates a change: Infers the target change name from context or lets you choose when ambiguous, then announces which change is being used.
  • Loads schema-aware apply instructions: Uses the OpenSpec CLI to detect the workflow schema, retrieve dynamic instructions, and handle blocked or finished states.
  • Executes tasks with guardrails: Reads the provided contextFiles, works through pending tasks one-by-one with minimal scoped changes, marks tasks complete, and pauses for unclear requirements or blockers.

Quick Start

Tell the system: run openspec-apply-change to implement the tasks for the specified 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 change tasks without losing workflow alignment?

To implement OpenSpec change tasks safely, use a schema-aware apply process that reads contextFiles, executes pending tasks with minimal scoped changes, and loops through checkboxes while pausing on ambiguity or blockers.

How does schema-aware task execution work for OpenSpec workflows?

Schema-aware task execution works by using the OpenSpec CLI in JSON mode to detect the workflow schema, retrieve dynamic apply instructions, and process pending tasks sequentially while updating task progress.

Can I resume an OpenSpec change implementation if it pauses on a blocker?

Yes, you can resume OpenSpec change implementation. The process supports starting, resuming, or progressing implementation across different schemas using CLI-driven selection and schema-aware apply instructions.

Do I need the OpenSpec CLI to apply changes to my workflow schemas?

Yes, you need the OpenSpec CLI to apply changes. The implementation requires using openspec status and openspec instructions apply in JSON mode to retrieve contextFiles and handle blocked or finished states safely.

What happens when OpenSpec task execution encounters unclear requirements?

When OpenSpec task execution encounters unclear requirements, errors, or blockers, the process pauses to prevent misalignment, ensuring minimal scoped changes are only made for well-defined tasks.

What is the best way to manage state and task progress for OpenSpec changes?

The best way to manage state for OpenSpec changes is using CLI-driven selection to infer target changes, loading schema-aware instructions, and updating task checkboxes as you loop through pending implementation tasks.