openspec-apply-change

Implements tasks from an OpenSpec change using CLI-driven status and instructions.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill openspec-apply-change-bill80362
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/skills/openspec-apply-change
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill openspec-apply-change-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of turning an OpenSpec change proposal into working code by walking through each task in the change, tracking progress, and pausing safely when requirements are unclear or blocked. ## Core Features & Use Cases - Change Selection: Resolves which change to work on from user input, conversation context, or the openspec list --json command when ambiguous. - Status-Aware Implementation: Reads openspec status and openspec instructions apply output to load the correct context files (proposal, specs, design, tasks) for the active 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 the skill, which reads the spec artifacts, implements each task with minimal scoped edits, checks off tasks as it goes, and suggests archiving when all tasks are done. ## Quick Start Ask the assistant to start implementing the tasks for your OpenSpec change, optionally naming the change to work on.

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 openspec 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 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 skill depends on commands like openspec status, openspec instructions apply, and openspec list to discover changes, schemas, context files, and task progress.

What does the skill do when a change is blocked or already complete?

For a blocked state with missing artifacts, it shows the issue and suggests continuing the change workflow. For an all_done state, it congratulates you and suggests archiving the change instead of editing.

Can it edit files in a workspace-planning change?

No. When status reports workspace-planning mode with empty allowedEditRoots, it treats linked repos as read-only context, asks you to select an affected area through an explicit implementation workflow, and stops before editing.