openspec-apply-change

Automate OpenSpec change task implementation with context files and status updates.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/Yager-42/-- --skill openspec-apply-change-yager-42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Yager-42/--/tree/main/.codex/skills/openspec-apply-change
Command: npx skills add https://github.com/Yager-42/-- --skill openspec-apply-change-yager-42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing tasks from an OpenSpec change can be error-prone and time-consuming without clear guidance and automation. This skill automates the workflow to select, fetch context, and drive task execution, reducing manual coordination.

Core Features & Use Cases

  • Change selection and context resolution: determines the change to apply, infers from conversation context, or prompts the user when ambiguous.
  • Status-aware guidance: reads schema status and progress, handles blocked or completed states.
  • Stepwise task implementation: iterates through pending tasks, updates task status, and provides dynamic instructions.

Quick Start

Start the OpenSpec change implementation by selecting a change name or inferring it from context.

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 tasks in my project?

Automating OpenSpec change implementation requires the OpenSpec CLI to select a specific change, fetch its context files, and drive stepwise task execution while updating task checkboxes and handling blocked or completed states.

How does status-aware guidance work when applying changes to a project workspace?

Status-aware guidance reads the schema status and progress of a change to handle blocked or completed states, ensuring the implementation workflow pauses or resumes correctly based on current task completion.

Do I need the OpenSpec CLI to automate task execution and workflow changes?

Yes, the OpenSpec CLI is required to automate task execution, read apply instructions context files, and update task checkboxes dynamically while walking through pending change items.

Can I continue implementing a partially completed OpenSpec change from where I left off?

You can continue implementing a partially completed OpenSpec change by inferring the change name from conversation context or selecting it, allowing the workflow to iterate through remaining pending tasks.

What is the best way to handle blocked or completed tasks during change management automation?

Handling blocked or completed tasks during change management is done automatically through schema status resolution, which reads progress and dynamically provides instructions to bypass or conclude finished items.

Why does my OpenSpec change implementation prompt for a change name instead of inferring it?

OpenSpec change implementation prompts for a change name when the context is ambiguous, ensuring the correct change is selected before fetching context files and executing tasks.