openspec-apply-change

Automate OpenSpec change application with CLI status checks and task implementation.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/yjzaaa/learn-claude-code-my --skill openspec-apply-change-yjzaaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/yjzaaa/learn-claude-code-my/tree/main/.github/skills/openspec-apply-change
Command: npx skills add https://github.com/yjzaaa/learn-claude-code-my --skill openspec-apply-change-yjzaaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change requests are often fragmented between planning, status checks, and implementation. This Skill provides a guided, automated workflow to apply OpenSpec changes from inference to task execution, ensuring consistent progress.

Core Features & Use Cases

  • Orchestrates change selection from user input or context.
  • Checks change status, reads context files, and displays progress.
  • Implements pending tasks with minimal, scoped changes and dynamic guidance.

Quick Start

Provide a change name or let context infer it, then execute the OpenSpec apply workflow to implement pending tasks.

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate OpenSpec change implementation from start to finish?

Automating OpenSpec change implementation requires orchestrating change selection, checking status, reading context files, and executing pending tasks. This workflow handles multiple changes, blocking states, and incremental task progress automatically.

What is the best way to manage multiple OpenSpec changes with blocking states?

Managing multiple OpenSpec changes with blocking states involves orchestrated status checks and incremental task implementation. The workflow reads JSON outputs, updates task checkboxes, and handles blocking states dynamically to ensure consistent progress.

Do I need the openspec CLI to automate task implementation?

Yes, automating task implementation requires the openspec CLI. The workflow depends on the CLI to read JSON outputs, update task checkboxes, and read context files to guide scoped implementation of pending tasks.

How does OpenSpec apply workflow handle context files during code changes?

The OpenSpec apply workflow reads context files to guide minimal, scoped changes during task implementation. It uses dynamic guidance from these files to ensure consistent progress and update task checkboxes accurately.

Can I apply OpenSpec changes incrementally across pending tasks?

Yes, applying OpenSpec changes incrementally across pending tasks is supported. The workflow orchestrates task implementation, updates task checkboxes, and maintains incremental progress even when encountering blocking states.

Why does my OpenSpec change workflow fragment between planning and implementation?

OpenSpec change workflows fragment when planning, status checks, and implementation are disconnected. A guided automated workflow bridges these phases by orchestrating selection, context reading, and scoped task execution to ensure consistent progress.