openspec-apply-change

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

Updated Jun 25, 2026

Search Tags:#spec-driven #software development #change management #openspec #task implementation #cli workflow

Ready to run

npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-apply-change-ismaelsoilet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-apply-change-ismaelsoilet

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 approved artifacts. ## Core Features & Use Cases - Change Selection: Resolves the target change from user input, conversation context, or by listing active changes when ambiguous. - Status-Aware Implementation: Reads schema, context files, and task state via `openspec status` and `openspec instructions apply` before writing any code. - Task Loop with Guardrails: Implements tasks one by one, marks checkboxes complete, and pauses on ambiguity, design issues, or errors instead of guessing. - Use Case: A developer has a spec-driven change with 7 pending tasks; invoking this skill implements each task in order, updates the tasks file, and reports when the change is ready to archive. ## Quick Start Ask the assistant to start implementing the tasks for your OpenSpec change, optionally naming the change to work on.

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 an optional change name. 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 in the tasks file.

What happens if no change name is provided?▼

The skill infers the change 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 before proceeding.

Does openspec-apply-change require the openspec CLI?▼

Yes, the skill requires the openspec CLI to be installed. All state reads and writes, including status, instructions, and validation, go through openspec commands, optionally scoped with a --store flag.

What does the skill do when a change is blocked or already complete?▼

For a blocked state it shows the missing artifacts and suggests creating them via the appropriate instructions command. For an all-done state it congratulates you and suggests archiving the change.

When does implementation pause instead of continuing?▼

It pauses when a task is unclear, when implementation reveals a design issue in the artifacts, when an error or blocker occurs, or when the user interrupts. It reports options and waits for guidance rather than guessing.