openspec-apply-change

Implement tasks from an OpenSpec change using the openspec CLI.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-apply-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-apply-change-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns OpenSpec change proposals into working code by walking through each task in a change, tracking progress, and keeping implementation aligned with the approved specs and design artifacts. ## Core Features & Use Cases - Change Selection and Status: Resolves the target change by name, context, or interactive selection, then reads schema, progress, and task state via openspec status and openspec instructions apply. - Guided Task Implementation: Reads the change's context files (proposal, specs, design, tasks), implements each pending task, and marks checkboxes complete as work finishes. - Guardrails and Pause Handling: Blocks on missing artifacts, ambiguous tasks, or scope creep, surfacing issues and options instead of guessing. - Use Case: After drafting an OpenSpec change for a new API endpoint, run the apply workflow to implement all seven tasks in order, with progress reported after each one. ## Quick Start Ask the assistant to start implementing the tasks for your OpenSpec change, optionally naming the change, for example by saying to apply the change add-auth.

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?▼

Select the change by name or let it be inferred from context, then the workflow runs openspec status and openspec instructions apply to load tasks. Each pending task is implemented in order and its checkbox is marked complete in the tasks file.

What is OpenSpec and how does the apply workflow use it?▼

OpenSpec is a spec-driven change management workflow driven by the openspec CLI. The apply step reads a change's artifacts such as proposal, specs, design, and tasks, then implements each task while reporting progress.

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

Yes, the skill requires the openspec CLI to be installed and available. All state, instructions, and task progress come from commands like openspec status, openspec list, and openspec instructions apply.

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

When status reports a blocked state, the workflow stops and shows which artifact is missing. It suggests creating the next artifact using openspec instructions for that artifact before implementation can continue.

Can I apply an OpenSpec change stored in a registered store?▼

Yes, run openspec store list --json to discover registered store ids, then pass --store <id> on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.