openspec-apply-change

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

Updated Jul 1, 2025
One-click install
npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-apply-change-mosakuzii0216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/mosakuzii0216/mosaku-v1/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-apply-change-mosakuzii0216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of turning an OpenSpec change plan into working code by walking through each task in the change, tracking progress, and keeping implementation aligned with the proposal, specs, and design artifacts. ## Core Features & Use Cases - Guided task implementation: Selects a change, reads its status and apply instructions via the openspec CLI, then works through pending tasks one by one. - Progress tracking: Marks tasks complete in the tasks file as it goes and reports "N/M tasks complete" status at every stage. - Blocked-state handling: Detects missing artifacts, paused states, and design issues, then prompts for clarification instead of guessing. - Use Case: After drafting a spec-driven change with proposal and tasks, ask the assistant to implement it; it reads the context files, codes each task, checks them off, and suggests archiving when done. ## Quick Start Ask the assistant to implement the OpenSpec change named add-auth and work through its tasks.

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 this skill?

Provide a change name or let the skill infer one from context. It runs openspec status and instructions commands, reads the context files, then implements 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, auto-selects if only one active change exists, or lists available changes via openspec list --json and asks you to pick one.

Does this skill require the openspec CLI?

Yes, the openspec CLI is a hard requirement. All status checks, apply instructions, and change selection run through openspec commands, and the skill declares compatibility requiring it.

What does the skill do when a change is blocked?

When the CLI reports a blocked state due to missing artifacts, it shows the message and suggests creating the missing artifact, either via the continue command or by requesting instructions for the next artifact.

How does the skill handle multiple OpenSpec stores?

If you name a store, it runs openspec store list --json to find registered store ids, then appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.