openspec-apply-change

Implements tasks from an OpenSpec change using the openspec CLI.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-apply-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/zh-impact/agent-feeder/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-apply-change-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an OpenSpec change proposal into working code requires manually tracking tasks, reading scattered context files, and updating checklists. This Skill automates that loop by driving the openspec CLI to select a change, load its context, and implement tasks one by one. ## Core Features & Use Cases - Change Selection: Infers the target change from conversation context or lists active changes via openspec list --json when ambiguous. - Schema-Aware Context Loading: Runs openspec status and openspec instructions apply to discover which artifacts (proposal, specs, design, tasks) to read for the active workflow schema. - Guided Task Implementation: Works through pending tasks, marks each checkbox complete in the tasks file, and pauses on blockers, ambiguity, or design issues. - Use Case: After drafting an OpenSpec change for a new API endpoint, invoke this Skill to read the proposal and tasks, implement each task in the codebase, and track progress until all tasks are complete and ready to archive. ## Quick Start Ask the assistant to start implementing the tasks from your current OpenSpec change, optionally naming the change to apply.

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 apply workflow with an optional change name. It runs openspec status and openspec instructions apply to load context files, then implements each pending task and marks its checkbox complete in the tasks file.

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

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

Does openspec-apply-change require the openspec CLI?▼

Yes, the openspec CLI is required. The workflow depends on commands like openspec status, openspec instructions apply, and openspec list to discover schemas, context files, and task progress.

What happens when an OpenSpec change is blocked or missing artifacts?▼

When the status returns a blocked state due to missing artifacts, the workflow shows the issue and suggests continuing artifact creation first instead of attempting implementation.

Can I pause implementation if a task is unclear or reveals a design issue?▼

Yes. The workflow pauses on ambiguous tasks, errors, or design problems discovered during implementation, reports the issue with options, and suggests updating the change artifacts before continuing.