openspec-apply-change

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

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-apply-change-miftah-fentaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Miftah-Fentaw/GymPulse/tree/main/.qwen/skills/openspec-apply-change
Command: npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-apply-change-miftah-fentaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved OpenSpec change proposal into working code requires tracking task status, reading the right context artifacts, and updating checklists consistently, which is error-prone when done manually. ## Core Features & Use Cases - Change Selection and Status Tracking: Selects a change by name or context, then parses openspec status JSON to understand the 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 work finishes. - Blocked-State and Pause Handling: Detects blocked or all-done states, surfaces design issues or scope creep, and pauses for user guidance instead of guessing. - Use Case: After drafting an OpenSpec change for a new authentication feature, run this Skill to work through every task in the tasks file, updating code and checkboxes until the change is 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".

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, or let it be inferred from context. The skill runs openspec status and openspec instructions apply to load tasks and context files, then implements each pending task and marks its checkbox complete.

What is the openspec CLI used for in spec-driven development?▼

The openspec CLI manages changes, specs, and workflow artifacts in an OpenSpec repository. Commands like status, instructions, list, show, and validate report progress and return the context files needed to implement a change.

Can I apply an OpenSpec change stored in 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. The flag stays sticky for the rest of the workflow once selected.

What happens if an OpenSpec change is blocked during implementation?▼

When status returns state blocked, the skill shows the missing artifacts message and suggests continuing with the next artifact instead of implementing. It never bypasses a CLI-controlled blocked state.

When should I not mark an OpenSpec task as complete?▼

Only mark a task complete when its specified behavior is fully implemented. If implementation reveals extra scope, design issues, or unclear requirements, pause and ask rather than silently narrowing or deferring the work.