orchestrator

Route implementation tasks to child agents while tracking branch ownership and status.

9|Updated Feb 14, 2026

Search Tags:#claude code #agent orchestration #branch management #parallel development #workflow routing #child agents

Ready to run

npx skills add https://github.com/koolamusic/claudefiles --skill orchestrator-koolamusic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/koolamusic/claudefiles/tree/main/skills/orchestrator
Command: npx skills add https://github.com/koolamusic/claudefiles --skill orchestrator-koolamusic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents long-running coordination sessions from becoming overloaded with implementation details by separating planning, routing, and branch ownership from execution work.

Core Features & Use Cases

Durable Agent Routing: Maintains a coordination thread that delegates branch-specific implementation tasks to reusable child agents.
Branch Context Management: Tracks ownership, status, blockers, and follow-up work through a persistent branch table within the session.
Use Case: Manage multiple feature branches or tickets by acting as a chief-of-staff that routes coding work while preserving a clear overview of progress.

Quick Start

Use the orchestrator skill to turn this session into a coordination thread that routes implementation tasks to child agents.

Frequently Asked Questions about orchestrator

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

FAQPage Schema

How do I coordinate parallel agent execution across multiple branches without losing context?▼

You can maintain a coordination thread that routes implementation tasks to reusable child agents while tracking branch ownership and status. This preserves the main session context from being overloaded with execution details.

What is agent orchestration in software engineering workflows?▼

Agent orchestration separates planning and routing from execution by delegating branch-specific implementation work to child agents. A coordination thread maintains a persistent branch table to track ownership, status, and blockers.

How do I manage branch ownership and status during parallel development?▼

Branch ownership and status are managed through a persistent branch table within the coordination session. This table tracks ownership, status, blockers, and follow-up work for each branch routed to reusable child agents.

Can I use worktree isolation to manage multiple feature branches with child agents?▼

Yes, worktree isolation is used to safely coordinate reusable child agents across multiple feature branches. This isolation maintains clear branch ownership boundaries while parallel development tasks are executed.

Why does my coordination session lose context when handling multiple pull requests?▼

Coordination sessions lose context when they become overloaded with implementation details from handling multiple pull requests. Routing execution work to child agents and maintaining a persistent branch table preserves the main session's overview.

What is the best way to route implementation work away from planning sessions?▼

The best way is to use a coordination thread that acts as a chief-of-staff, delegating coding tasks to reusable child agents. This durable agent routing maintains a clear separation between planning and execution.