openspec-apply-change

Implement OpenSpec change tasks and update progress via the openspec CLI.

2.6k|399|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/Soju06/codex-lb --skill openspec-apply-change-soju06
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Soju06/codex-lb/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/Soju06/codex-lb --skill openspec-apply-change-soju06

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes 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 tasks are completed systematically.

Core Features & Use Cases

  • Task Implementation: Executes defined tasks from an OpenSpec change, updating progress as it goes.
  • 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 specification is defined in OpenSpec, this Skill can be used to systematically implement each task outlined in the change, ensuring all requirements are met.

Quick Start

Use the openspec-apply-change skill to implement 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 OpenSpec change task implementation, use this Skill to execute defined development steps sequentially. It retrieves instructions via the openspec CLI, applies spec-driven development, and systematically completes iterative tasks while tracking progress.

What is spec-driven development task automation and how does it manage workflows?

Spec-driven development task automation executes predefined tasks from a change specification to streamline workflows. It manages task completion by using the openspec CLI for status checks, retrieving instructions, and managing artifacts throughout the implementation process.

Do I need the openspec CLI to execute spec-driven development tasks?

Yes, executing spec-driven development tasks requires the openspec CLI. The Skill depends on the CLI to perform status checks, retrieve task instructions, and manage artifacts required for systematically applying changes to your workflow.

How do I implement tasks for a specific OpenSpec change like 'feature-x'?

To implement tasks for a specific OpenSpec change, provide the change name such as 'feature-x' to the Skill. If not explicitly provided, the Skill infers or prompts for the correct change to begin executing its defined development tasks.

Can I track progress automatically when applying OpenSpec changes to my workflow?

Yes, you can track progress automatically when applying OpenSpec changes. The Skill monitors task completion status and reports progress continuously as it executes each development step defined within the change specification.

What are the limitations of automating OpenSpec change implementation?

Automating OpenSpec change implementation is limited to workflows actively managed via OpenSpec. It requires the openspec CLI for artifact management and status checks, meaning it cannot execute tasks outside of a defined spec-driven development context.