openspec-apply-change

Implement OpenSpec change tasks sequentially and update artifacts.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pacaplan/flokay --skill openspec-apply-change-pacaplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/pacaplan/flokay/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/pacaplan/flokay --skill openspec-apply-change-pacaplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation of tasks defined within an OpenSpec change, streamlining the development process by guiding the user through task completion and artifact updates.

Core Features & Use Cases

  • Task Implementation: Executes defined tasks for a given OpenSpec change, updating code and marking tasks as complete.
  • Progress Tracking: Provides clear visibility into task completion status and overall progress.
  • Error Handling: Pauses and reports issues encountered during implementation, offering options for resolution.
  • Use Case: After a change has been designed and planned using OpenSpec, this skill can be invoked to write the actual code, update documentation, and ensure all defined tasks are addressed.

Quick Start

Use the openspec-apply-change skill to implement the tasks for the current 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 automate code implementation for spec-driven development tasks?

Automating code implementation for spec-driven development involves sequentially executing defined tasks and updating artifacts using the OpenSpec CLI to fetch change status and instructions. This skill guides task completion, code changes, and documentation updates.

What is the best way to track task completion status during OpenSpec changes?

Tracking task completion status during OpenSpec changes is handled by fetching the change status through the CLI, providing clear visibility into overall progress and marking tasks as complete once code changes are executed.

Do I need the OpenSpec CLI to implement change tasks?

Yes, you need the OpenSpec CLI to implement change tasks because it is required to fetch the change status, instructions, and context files necessary for guiding the sequential execution and artifact updates.

How does error handling work when applying spec-driven code changes?

Error handling when applying spec-driven code changes pauses the implementation upon encountering issues, reports the problem, and offers options for resolution before continuing with the remaining defined tasks.

When do I need to use a task automation workflow for OpenSpec changes?

You need to use a task automation workflow for OpenSpec changes after a change has been designed and planned, allowing you to write the actual code, update documentation, and ensure all defined tasks are addressed sequentially.