openspec-apply-change

Orchestrates per-task subagents to apply OpenSpec changes end-to-end.

10|1|Updated Apr 10, 2019
One-click install
npx skills add https://github.com/GeTechG/LDYOM --skill openspec-apply-change-getechg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/GeTechG/LDYOM/tree/main/LDYOM2/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/GeTechG/LDYOM --skill openspec-apply-change-getechg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align OpenSpec changes with automated task orchestration, reducing manual handoffs and ensuring consistent execution.

Core Features & Use Cases

  • Orchestrates end-to-end OpenSpec change implementation by delegating individual tasks to a per-task subagent.
  • Maintains a minimal orchestrator context (tasks.md, session.md) and robust session-state management.
  • Supports handling ambiguous changes with prompts and structured progress tracking for multi-task changes.

Quick Start

Provide the OpenSpec change name to begin applying tasks and let the orchestrator drive per-task execution.

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 OpenSpec change implementation across multiple tasks?

Automating OpenSpec change implementation involves orchestrating per-task subagents to execute tasks sequentially while maintaining session state and checking task statuses. You provide the change name, and the orchestrator drives the execution end-to-end.

What is per-task subagent orchestration for multi-task changes?

Per-task subagent orchestration delegates individual tasks of a change to separate subagents. This enforces safe delegation and non-editing of application code while maintaining a minimal orchestrator context for structured progress tracking.

How do I manage session state when applying staged OpenSpec changes?

Managing session state during staged execution requires maintaining minimal context files like tasks.md and session.md. The orchestrator tracks progress and gathers context automatically to ensure consistent execution across all tasks.

Can I use automated task orchestration for ambiguous OpenSpec changes?

Automated task orchestration supports ambiguous OpenSpec changes by issuing prompts to resolve uncertainties during execution. It structures progress tracking to handle multi-task changes safely without editing application code directly.

Why does the orchestrator enforce non-editing of application code during change implementation?

The orchestrator enforces non-editing of application code to ensure safe delegation of tasks to subagents. This prevents unintended modifications during staged execution while the orchestrator maintains session state and coordinates the overall change.

What do I need to start orchestrating OpenSpec changes end-to-end?

To start orchestrating OpenSpec changes, provide the change name to the orchestrator. It requires no external dependencies and automatically handles status checks, context gathering, and per-task execution for multi-task changes.