openspec-apply-change

Apply OpenSpec change tasks and update task checkboxes in repository files.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/daodaoedu/daodao --skill openspec-apply-change-daodaoedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/daodaoedu/daodao/tree/main/.gemini/skills/openspec-apply-change
Command: npx skills add https://github.com/daodaoedu/daodao --skill openspec-apply-change-daodaoedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines implementing work items defined in an OpenSpec change by guiding selection, reading context, and applying tasks until completion or pause. It removes manual steps of querying change status, locating context files, and tracking task progress so developers can focus on focused, incremental implementation.

Core Features & Use Cases

  • Change selection and discovery: Infers a change from context, auto-selects when only one active change exists, or prompts the user to choose from openspec list output.
  • Context-aware implementation loop: Fetches apply instructions, reads context files, shows progress, iterates through pending tasks, and updates task checkboxes as tasks complete.
  • State handling and guardrails: Detects blocked or all_done states, suggests follow-up actions (continue, archive, or update artifacts), pauses on ambiguity or errors, and enforces minimal, scoped changes.
  • Use Case: A developer wants to pick up an in-progress OpenSpec change, implement several pending tasks, and update progress atomically while consulting the spec and design files.

Quick Start

Begin implementing the change named "my-change" by running the openspec apply flow, reading the provided context files, and working through the listed tasks until completion or a blocker is reached.

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 pending work items from an OpenSpec change?

To implement pending work items from an OpenSpec change, this Skill fetches apply instructions via the openspec CLI, reads context files, iterates through tasks, and updates task checkboxes in repository files upon completion.

What is the best way to track task progress when applying changes across spec-driven workflows?

Tracking task progress across spec-driven workflows is handled by an automated context-aware implementation loop that iterates through pending tasks and atomically updates task checkboxes in repository files as each item completes.

Do I need the openspec CLI to apply change tasks to my repository?

Yes, you need the openspec CLI installed to apply change tasks, as the Skill requires the CLI to query change status, fetch apply instructions, read context files, and update task checkboxes in repository files.

How does change selection work when starting an implementation loop?

Change selection during the implementation loop infers the change from context, automatically selects when only one active change exists, or prompts you to choose from the openspec list output.

What happens if a task is blocked or all tasks are done during change implementation?

When a task is blocked or all tasks are done during change implementation, the Skill detects these states, pauses on ambiguity or errors, suggests follow-up actions like archiving, and enforces minimal scoped changes.