openspec-apply-change

Implement OpenSpec change tasks using the openspec CLI.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/deicer/codex-lb --skill openspec-apply-change-deicer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/deicer/codex-lb/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/deicer/codex-lb --skill openspec-apply-change-deicer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and 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 workflow and ensuring adherence to specifications.

Core Features & Use Cases

  • Task Implementation: Executes defined tasks from an OpenSpec change, updating progress and artifacts.
  • Contextual Awareness: Infers or prompts for the correct change if not explicitly provided.
  • Progress Tracking: Monitors and reports on task completion status.
  • Use Case: When a new feature is defined in OpenSpec, use this Skill to automatically start implementing the associated tasks, updating code and documentation as you go.

Quick Start

Use the openspec apply change skill to start implementing 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 automate implementation of tasks defined in an OpenSpec change?

To automate task implementation, use this Skill to execute schema-driven workflows. It handles task selection, reads artifacts, and iteratively implements development tasks while updating progress.

What is the best way to track progress when implementing OpenSpec changes?

Tracking progress for OpenSpec changes is handled automatically by the Skill. It monitors task completion status, updates artifacts, and reports on development progress throughout the implementation workflow.

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

Yes, the openspec CLI is required to apply changes. The Skill depends on this command-line interface for execution and for interacting with change artifacts during task automation.

Can I start implementing an OpenSpec change without specifying its name?

Yes, you can implement an OpenSpec change without explicitly specifying its name. The Skill features contextual awareness that automatically infers or prompts for the correct change to begin task execution.

How do schema-driven workflows handle task selection during feature implementation?

Schema-driven workflows manage task selection by reading change artifacts and checking task status. The Skill iteratively selects and executes the next available task based on the schema definitions.