openspec-apply-change

Implement tasks from an OpenSpec change using the openspec CLI.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-apply-change-gqadonis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-apply-change
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-apply-change-gqadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved OpenSpec change proposal into working code requires manually tracking tasks, reading scattered spec artifacts, and keeping checkboxes in sync. This Skill automates that loop by driving the openspec CLI to select a change, load its context files, and implement tasks one by one with progress tracking. ## Core Features & Use Cases - Change Selection and Status: 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 all context files (proposal, specs, design, tasks), implements each pending task, and marks checkboxes complete as it goes. - Guardrails and Pause Behavior: Pauses on ambiguity, blockers, or scope creep instead of guessing, and reports progress in structured output formats. - Use Case: A developer with an approved add-auth change runs the skill, which loads the spec-driven artifacts, implements all 7 tasks, and reports completion with a suggestion to archive the change. ## Quick Start Ask the assistant to implement the tasks from your OpenSpec change, optionally naming the change, for example: implement 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?

Invoke the skill with an optional change name, such as /skill:openspec-apply-change add-auth. It runs openspec status and openspec instructions apply to load context files, then implements each pending task and marks its checkbox complete.

How does the skill choose which change to work on?

It uses a provided name first, otherwise infers from conversation context or auto-selects when only one active change exists. If ambiguous, it runs openspec list --json and asks you to pick a change.

Does openspec-apply-change require the openspec CLI?

Yes, the skill requires the openspec CLI installed on the machine. All status, instructions, and listing operations are executed through openspec commands, and store-scoped workflows pass --store <id> to those commands.

What happens when a change is blocked or missing artifacts?

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

Can I update specs or design while implementing a change?

Yes, the workflow is fluid rather than phase-locked. If implementation reveals a design issue, the skill pauses and suggests updating the artifacts before continuing, instead of silently absorbing the extra scope.