openspec-apply-change

Implement tasks from an OpenSpec change using the openspec CLI.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/TranVanTienDat/Milkyway --skill openspec-apply-change-tranvantiendat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/TranVanTienDat/Milkyway/tree/main/agent-core/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/TranVanTienDat/Milkyway --skill openspec-apply-change-tranvantiendat

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 conversation context or lists available changes via openspec list --json when ambiguous. - Schema-Aware Execution: Reads openspec status and openspec instructions apply output 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 in the tasks file, and reports progress as N/M tasks complete. - Use Case: A developer has an approved OpenSpec change with 7 tasks. They invoke this Skill to work through each task, updating code and checkboxes until all tasks are done and the change is ready to archive. ## 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 apply workflow with an optional change name. It runs openspec status and openspec instructions apply to load context files, then works through each pending task, marking checkboxes complete in the tasks file as it goes.

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

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

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 resolve schemas, context files, and task progress.

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

When the apply instructions return 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 and resume an OpenSpec change later?▼

Yes, the workflow pauses on unclear tasks, errors, or design issues and reports current progress as N/M tasks complete. You can resume later since completed tasks are persisted as checked boxes in the tasks file.