openspec-apply-change

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

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-apply-change-ssttkkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/ssttkkl/finance-tracker/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-apply-change-ssttkkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an OpenSpec change's task list into actual code changes by driving the openspec CLI through selection, status checks, context loading, and task-by-task implementation with progress tracking. ## Core Features & Use Cases - Change Selection: Infers the target change from conversation context, auto-selects when only one active change exists, or lists available changes for the user to pick. - Schema-Aware Execution: Reads status and apply instructions from the openspec CLI to discover the workflow schema, context files, progress, and blocked or completed states. - Task Implementation Loop: Works through pending tasks one by one, marking each checkbox complete in the tasks file, and pauses on ambiguity, design issues, or errors. - Use Case: A developer has a spec-driven change with 7 tasks defined in OpenSpec and asks the assistant to implement them; the skill reads the proposal, specs, design, and tasks, then implements each task while reporting progress. ## Quick Start Ask the assistant to start implementing the tasks for a named OpenSpec change, optionally specifying a registered store.

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 a change name or let it infer one from context. It runs openspec status and openspec instructions apply to load context files and the task list, then implements each pending task and marks its checkbox complete.

How does the skill choose which OpenSpec 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 to be installed, since all status, instructions, list, and store operations are executed through openspec commands. It is restricted to Bash openspec invocations.

What happens when an OpenSpec change is blocked or missing artifacts?

When the apply instructions return a blocked state, the skill shows the message and suggests creating the missing artifact, either via openspec-continue-change or by running openspec instructions for the next artifact directly.

Can I use openspec-apply-change with a registered store?

Yes, run openspec store list --json to discover registered store ids, then pass --store <id> on commands that read or write specs and changes. Commands without a store act on the nearest local openspec root.