openspec-apply-change

Automate OpenSpec change tracking and task checkbox updates via CLI.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/foxytanuki/bob --skill openspec-apply-change-foxytanuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/foxytanuki/bob/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/foxytanuki/bob --skill openspec-apply-change-foxytanuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec changes often require a guided, repeatable process to select, track, and implement tasks until they are completed.

Core Features & Use Cases

  • Guided change selection and progress tracking for OpenSpec changes.
  • Read and apply change instructions, statuses, and context files to drive incremental implementation.
  • Handle blocked, all_done, and in-progress states with clear prompts and automated status updates.

Quick Start

Provide a change name or let the system infer it, then iteratively implement all pending tasks from the OpenSpec change until completion.

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 tracking and applying OpenSpec changes end-to-end?

Automate OpenSpec changes by using a guided workflow to select, track, and implement tasks. The system interacts with the openspec CLI to fetch status, read context files, and update task checkboxes until completion.

What is the best way to manage blocked or in-progress OpenSpec change tasks?

Manage blocked or in-progress OpenSpec tasks through automated status updates and clear prompts. The workflow detects your current change state, reads instructions, and guides you through incremental implementation steps.

How do I start a new OpenSpec change and iteratively implement pending tasks?

Start a new OpenSpec change by providing a change name or letting the system infer it. The workflow then drives iterative implementation of all pending tasks, applying instructions and updating progress automatically.

Does OpenSpec change automation require CLI integration to fetch status and context files?

OpenSpec change automation relies on CLI integration to fetch status and instructions. It interacts directly with the openspec CLI to read context files and update task checkboxes as work progresses.

How does the OpenSpec workflow handle completed or all_done change states?

The OpenSpec workflow handles all_done change states by verifying all tasks are checked. It reads context files and applies instructions to ensure every pending task is completed and tracked accurately.