openspec-apply-change

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-apply-change-javakishore-veleti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-apply-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-apply-change-javakishore-veleti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an OpenSpec change proposal into working code requires tracking task status, reading the right context artifacts, and updating checkboxes consistently, which is error-prone when done manually. ## Core Features & Use Cases - Change Selection and Status Tracking: Selects a change by name or inference, then parses openspec status and openspec instructions apply JSON output to understand schema, progress, and remaining tasks. - Guided Task Implementation Loop: Reads context files (proposal, specs, design, tasks), implements each pending task, and marks checkboxes complete as it goes. - Blocked and Paused State Handling: Detects blocked or all-done states, pauses on ambiguity or errors, and reports progress with structured output. - Use Case: After drafting an OpenSpec change for a new feature, run this skill to work through every task in the tasks file until the change is fully implemented and ready to archive. ## Quick Start Ask the assistant to implement the tasks from your OpenSpec change, for example by saying "apply the add-auth change". ## Quick Start Use this skill to implement all pending tasks from the OpenSpec change named add-auth.

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?

Run the apply workflow with a change name, and it calls openspec status and openspec instructions apply to load context files and the task list. It then implements each pending task and marks its checkbox complete in the tasks file.

How does the skill choose which OpenSpec change to apply?

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

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

When the CLI reports a blocked state, the skill shows the message and suggests creating the missing artifact, using openspec status and openspec instructions for the next artifact. It does not bypass blocked states.

Does openspec apply work with registered stores?

Yes. If the work lives in a registered store, it runs openspec store list --json to find the store id and appends --store <id> to commands that read or write specs and changes for the rest of the workflow.

When should I pause instead of continuing task implementation?

Pause when a task is unclear, implementation reveals a design issue, or an error occurs. The skill reports the issue with options and waits for guidance rather than guessing.