openspec-apply-change

Implement tasks from an OpenSpec change using the openspec CLI.

1|1|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/33may/robotics --skill openspec-apply-change-33may
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/33may/robotics/tree/main/humanoid/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/33may/robotics --skill openspec-apply-change-33may

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the manual effort of tracking and executing implementation tasks defined in an OpenSpec change, keeping task checkboxes, progress, and context files synchronized during development. ## Core Features & Use Cases - Change Selection: Automatically infers the active change from context or lists available changes via openspec list --json when ambiguous. - Schema-Aware Execution: Reads status and apply instructions from the openspec CLI to load the correct context files (proposal, specs, design, tasks) for any workflow schema. - Task Loop with Progress Tracking: Implements each pending task, marks checkboxes complete, and reports progress as N/M tasks done. - Use Case: A developer has a spec-driven change with 7 pending tasks and asks the assistant to implement them; the skill reads the change artifacts, works through each task, updates the tasks file, and reports completion. ## Quick Start Ask the assistant to start implementing the tasks for your current OpenSpec change, optionally naming the change explicitly.

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 tasks from an OpenSpec change?

Invoke the skill with an optional change name; it runs openspec status and instructions apply to load context files, then works through each pending task, marking checkboxes complete as it goes.

What happens if I don't specify a change name?

The skill infers the change from conversation context, auto-selects when only one active change exists, or runs openspec list --json and asks you to pick when multiple changes are available.

Does openspec-apply-change require the openspec CLI?

Yes, the openspec CLI is a hard requirement. The skill shells out to openspec status, openspec instructions apply, and openspec list to discover schema, context files, and task state.

What happens when a change is blocked or missing artifacts?

When the apply instructions return state blocked, the skill shows the missing-artifact message and suggests using openspec-continue-change instead of attempting implementation.

Can it edit files outside the allowed workspace roots?

No. If status reports workspace-planning mode with empty allowedEditRoots, the skill treats linked repos as read-only, asks you to select an affected area, and stops before editing.