openspec-apply-change

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-apply-change-kevmendesdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/KevMendesDev/mercadinho-sao-francisco/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-apply-change-kevmendesdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an OpenSpec change's task list into actual code by guiding the AI through selecting the change, reading its context files, implementing each pending task, and tracking progress until completion. ## Core Features & Use Cases - Change Selection and Status: Resolves the target change by name, context, or interactive prompt, then reads schema, progress, and task state via openspec status and openspec instructions apply. - Guided Task Implementation: Reads all context files (proposal, specs, design, tasks), implements each pending task with minimal scoped edits, and marks tasks complete in the tasks file. - Guardrails and Pause Handling: Pauses on ambiguity, design issues, scope creep, or blockers instead of guessing, and reports structured progress output. - Use Case: A developer has an approved OpenSpec change with 7 tasks and asks the AI to implement it; the skill works through each task, checks them off, and suggests archiving when done. ## Quick Start Ask the AI to implement the OpenSpec change named add-auth by running the openspec-apply-change skill with that change name.

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 an OpenSpec change with an AI agent?▼

Invoke the apply-change workflow with a change name, or let it infer one from context. It runs openspec status and instructions apply, reads the context files, then implements each pending task and marks it complete in the tasks file.

How do I implement tasks from an OpenSpec spec-driven workflow?▼

Run openspec instructions apply --change "<name>" --json to get contextFiles, progress, and the task list. Read every listed file such as proposal, specs, design, and tasks, then implement tasks one by one, checking each off as done.

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

Yes, the skill requires the openspec CLI installed on the machine. All state, instructions, and progress come from commands like openspec status, list, and instructions apply, optionally scoped with --store for registered stores.

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

When the apply instructions return state blocked, the skill shows the message and suggests creating the missing artifact, for example via the continue-change workflow or openspec instructions for the next artifact. It does not bypass the blocked state.

When should I pause instead of completing an OpenSpec task?▼

Pause when a task is unclear, implementation reveals a design issue, the work exceeds what the spec describes, or an error occurs. Only mark a task complete when its specified behavior is fully implemented, never partially.