openspec-apply-change

Implement tasks from an OpenSpec change using the openspec CLI.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/hpelaez73/elprado-backend --skill openspec-apply-change-hpelaez73
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/hpelaez73/elprado-backend/tree/main/.trae/skills/openspec-apply-change
Command: npx skills add https://github.com/hpelaez73/elprado-backend --skill openspec-apply-change-hpelaez73

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 pausing safely when requirements are unclear or blocked. ## Core Features & Use Cases - Change Selection: Automatically infers the active change from context, lists available changes when ambiguous, and supports registered OpenSpec stores via --store flags. - Guided Task Implementation: Reads apply instructions and context files (proposal, specs, design, tasks) from the openspec CLI, then implements each pending task and marks it complete in the tasks file. - State Handling and Guardrails: Detects blocked and all-done states, surfaces scope creep instead of silently narrowing behavior, and reports progress after every session. - Use Case: After drafting a spec-driven change for a new authentication feature, run this Skill to implement all seven planned tasks one by one, with checkboxes updated in the tasks file and a completion summary at the end. ## Quick Start Ask the assistant to implement the tasks for 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, such as /openspec-apply-change add-auth. The skill runs openspec status and openspec instructions apply to load context files, then implements each pending task and marks it complete in the tasks file.

How do I apply an OpenSpec change stored in a registered 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 store flag stays sticky for the rest of the workflow.

What happens if the change name is ambiguous or missing?

The skill first tries to infer the change from conversation context and auto-selects when only one active change exists. If still ambiguous, it runs openspec list --json and asks you to pick a change.

Why does the apply workflow show a blocked state?

A blocked state means required artifacts are missing for the change. The skill suggests creating the next artifact, which you can inspect with openspec status and openspec instructions for the specific artifact id.

Can I pause implementation when a task is unclear?

Yes. The skill pauses on unclear tasks, design issues, errors, or scope beyond the spec, and asks for guidance rather than guessing. It never marks a task complete unless the specified behavior is fully implemented.