openspec-apply-change

Automate OpenSpec change application with status checks and task execution.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-apply-change-lippyydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/LippyyDev/Agate-Antigravity-Helper-/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-apply-change-lippyydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end process of applying an OpenSpec change by orchestrating change selection, status inspection, and task execution across the change lifecycle.

Core Features & Use Cases

  • Select and validate an OpenSpec change, using context to infer the target when not explicitly provided.
  • Retrieve apply instructions and context files, handle different schema states (blocked, all_done, in_progress), and present guidance for next steps.
  • Iteratively implement tasks, update task checkboxes, and report progress until the change is fully applied.

Quick Start

Provide a change name to start applying, or let the assistant infer it from context and proceed.

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 management from start to finish?

Automating OpenSpec change management involves orchestrating change selection, status checks, and task execution end-to-end. The workflow guides you through selecting a change, fetching status, reading context files, implementing tasks, and updating checkboxes until completion.

What is an OpenSpec change workflow and how does it handle different states?

An OpenSpec change workflow is an automated process that drives implementation by reading apply outputs. It handles blocked, all_done, and ongoing states by retrieving apply instructions, presenting guidance for next steps, and iteratively implementing tasks.

How do I apply an OpenSpec change when the target name is not specified?

To apply an OpenSpec change without an explicit name, the assistant infers the target change from the current context. Once inferred, it proceeds to validate the change, fetch its status, and obtain the necessary implementation instructions.

Can I use CLI task automation to update task checkboxes iteratively?

Yes, CLI task automation can iteratively implement tasks and update task checkboxes. It reads context files, displays progress, executes the implementation, and marks checkboxes until the OpenSpec change is fully applied.

What should I do when an OpenSpec change status is blocked?

When an OpenSpec change status is blocked, the workflow retrieves apply instructions and context files to present specific guidance for next steps. You must resolve the block before proceeding with task implementation and checkbox updates.

Do I need dependencies to run the OpenSpec apply change workflow?

No external dependencies are required to run the OpenSpec apply change workflow. It operates independently to select changes, fetch status, read context files, and implement tasks until the change lifecycle is complete.