openspec-apply-change

Implements tasks from an OpenSpec change using the openspec CLI workflow.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill openspec-apply-change-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/JhonMA82/api-starter --skill openspec-apply-change-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of turning an OpenSpec change proposal into working code by walking through the change's task list, reading the right context files, and tracking progress until every task is done. ## Core Features & Use Cases - Change selection and status inspection: Resolves the target change from user input or conversation context, then reads schema, progress, and task state via openspec status and openspec instructions apply. - Guided task implementation loop: Reads the context files (proposal, specs, design, tasks), implements each pending task, and marks checkboxes complete as it goes. - State-aware handling: Detects blocked and all-done states, suggests the next artifact or archiving, and pauses with structured options when ambiguity or errors appear. - Use Case: After drafting a spec-driven change for a new API endpoint, ask the assistant to apply the change and it will implement each task in order, updating the tasks file and reporting progress. ## Quick Start Ask the assistant to implement the tasks from your OpenSpec change, optionally naming the change, for example by saying to apply the add-auth change.

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

Run the apply workflow with a change name, or let it be inferred from context. The skill runs openspec status and openspec instructions apply to load the task list and context files, then implements each pending task and marks it complete.

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

The skill tries to infer the change from conversation context or auto-selects it when only one active change exists. If the choice is ambiguous, it lists available changes with openspec list --json and asks you to pick one.

Does openspec apply work with multiple OpenSpec stores?▼

Yes. If the work lives in a registered store, the skill runs openspec store list --json to discover store ids and appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.

What does the skill do when a change is blocked?▼

When the apply instructions return a blocked state due to missing artifacts, it shows the message and suggests creating the next artifact, either via the continue skill or by running openspec instructions for the required artifact id.

When does the implementation loop pause instead of continuing?▼

It pauses when a task is unclear, when implementation reveals a design issue in the artifacts, when an error or blocker occurs, or when the user interrupts. It reports the issue with options and waits for guidance rather than guessing.