openspec-apply-change

Implement OpenSpec change tasks and update their statuses.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Tzeusy/butlers --skill openspec-apply-change-tzeusy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Tzeusy/butlers/tree/main/.gemini/skills/openspec-apply-change
Command: npx skills add https://github.com/Tzeusy/butlers --skill openspec-apply-change-tzeusy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the implementation of tasks defined within an OpenSpec change, ensuring that development work aligns with specified requirements and progresses efficiently.

Core Features & Use Cases

  • Task-driven Implementation: Executes specific tasks outlined in an OpenSpec change, updating their status as they are completed.
  • Contextual Awareness: Reads necessary context files and understands the current state of the change to guide implementation.
  • Use Case: When a new feature is defined in OpenSpec, this Skill can be used to systematically implement each task, from writing code to updating documentation, ensuring all aspects of the change are addressed.

Quick Start

Use the openspec apply change skill to implement the tasks for the change named 'feature-x'.

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 defined in an OpenSpec change?

To implement OpenSpec change tasks, this Skill parses JSON output from the openspec CLI to understand schema, context files, and current task status, then systematically executes each task while managing progress and updating statuses.

What is the best way to manage blocked or completed states in spec-driven workflows?

Managing blocked or 'all_done' states in spec-driven workflows involves parsing JSON output from the openspec CLI to track task status, allowing the Skill to handle various implementation states and update progress efficiently.

Do I need the openspec CLI installed to apply changes to my development workflow?

Yes, you need the openspec CLI installed and configured, because this Skill requires it to parse JSON output for schema details, context files, and task status during spec-driven task implementation.

How does this approach handle context files during task implementation?

Handling context files during task implementation works by reading necessary context and parsing openspec CLI JSON output to understand the current state of the change, which guides the subsequent code and documentation updates.

Can I systematically execute feature development tasks from writing code to updating documentation?

Yes, you can systematically execute feature development tasks from writing code to updating documentation, because the Skill reads context files and manages task status to ensure all aspects of an OpenSpec change are addressed.