orchestration

Coordinate sub-agents to decompose work into sub-issues and delegate tasks.

Updated Apr 19, 2026

Search Tags:#subagents #delegation #project-management #orchestrate #task-decomposition #knowledge-persistence #issue-workflow

Ready to run

npx skills add https://github.com/georgernstgraf/aitranscribe-windows --skill orchestration-georgernstgraf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestration
Source: https://github.com/georgernstgraf/aitranscribe-windows/tree/main/skills/orchestration
Command: npx skills add https://github.com/georgernstgraf/aitranscribe-windows --skill orchestration-georgernstgraf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires issue-workflow, knowledge-persistence.

What problem does it solve?

Orchestrate sub-agents to decompose, delegate, and deliver work via issue-driven task decomposition. Its sole responsibilities are to bootstrap project context before starting any task, to decompose work into well-scoped sub-issues, to delegate each sub-issue to a Task agent for implementation, and to collect results, verify correctness, and advance to the next sub-issue.

Core Features & Use Cases

Pure orchestrator that never writes code; it reads, plans, decomposes, delegates, verifies, and persists. Implementation belongs to Task agents.
Use this skill when coordinating multiple sub-tasks, managing an epic with sub-issues, or acting as a dispatcher for Task agents.
Works alongside companion skills issue-workflow for GitHub issue lifecycle operations and knowledge-persistence for persisting session context.

Quick Start

Bootstrap the project context, decompose the work into sub-issues, and delegate each sub-issue to a Task agent to begin execution.

Frequently Asked Questions about orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate multiple sub-agents to decompose and deliver complex project tasks?▼

To coordinate sub-agents for complex project tasks, use an orchestration skill that bootstraps context, decomposes work into sub-issues, and delegates each to a Task agent for implementation. It reads, plans, verifies, and persists without writing code itself.

What is issue-driven task decomposition for managing epics with sub-agents?▼

Issue-driven task decomposition is a method where an orchestrator breaks down an epic into well-scoped sub-issues, delegates them to Task agents, and collects results to advance sequentially. This ensures structured multi-task delivery and epic-level governance.

Do I need GitHub issue-workflow and knowledge-persistence skills to orchestrate sub-agents?▼

Yes, issue-workflow and knowledge-persistence are required dependencies. The orchestrator works alongside issue-workflow for GitHub issue lifecycle operations and knowledge-persistence for saving session context during sub-agent delegation.

How do I start dispatching sub-issues to Task agents for multi-task work?▼

To start dispatching sub-issues, bootstrap the project context, decompose the work into well-scoped sub-issues, and delegate each sub-issue to a Task agent. The orchestrator will then verify correctness and advance to the next task.

Why does the orchestrator not write code when managing sub-agent task delegation?▼

The orchestrator does not write code because it is designed as a pure orchestrator that reads, plans, decomposes, delegates, verifies, and persists. All implementation work belongs exclusively to the delegated Task agents.