openspec-apply-change

Implement tasks from an OpenSpec change using the openspec CLI.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-apply-change-joeshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/JoeShi/coding-agent-usage-montior/tree/main/.kimi-code/skills/openspec-apply-change
Command: npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-apply-change-joeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an OpenSpec change's task list into working code by guiding the AI through selecting the change, reading its context files, implementing each task, and tracking progress until completion. ## Core Features & Use Cases - Change Selection: Picks a change by name, conversation context, or by listing available changes when ambiguous, with support for named OpenSpec stores via --store. - Status-Aware Workflow: Reads openspec status and openspec instructions apply JSON output to understand the schema, progress, context files, and blocked or all-done states. - Task Implementation Loop: Works through pending tasks one by one, marking each - [x] in the tasks file, and pauses on ambiguity, design issues, or scope creep instead of guessing. - Use Case: After drafting a spec-driven change with proposal, design, and tasks, invoke this skill to have the AI implement all seven tasks sequentially and report "7/7 tasks complete" with an archive suggestion. ## Quick Start Ask the AI to implement the tasks from your OpenSpec change, optionally naming the change, for example: start implementing 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 works through each pending task and marks it complete in the tasks file.

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

The skill infers the change from conversation context or auto-selects it when only one active change exists. If the choice is ambiguous, it runs openspec list --json and asks you to pick one before proceeding.

Does openspec-apply-change require the openspec CLI?

Yes, the skill requires the openspec CLI to be installed, since every step (status, instructions, list, store discovery) is executed through openspec commands. Without a named store, commands act on the nearest local openspec/ root.

How do I use this skill with a named OpenSpec store?

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

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

For a blocked state with missing artifacts, it shows the message and suggests creating the next artifact or using openspec-continue-change. For an all-done state, it congratulates you and suggests archiving the change.

When does the skill pause instead of continuing implementation?

It pauses when a task is unclear, implementation reveals a design issue, work exceeds what the spec describes, or an error occurs. It reports the issue with options and waits for guidance rather than silently narrowing scope.