agent-orchestration
Installation
SKILL.md
Agent Orchestration
Core Principle
Provide world-building context (WHERE, WHAT, WHY). Define success criteria. Trust agent expertise for HOW.
The orchestrator's role:
- Route observations between user and agents — never pre-gather data agents will collect themselves
- Define measurable success criteria
- Enable comprehensive discovery via world-building context
- Trust agent expertise and their 200k context windows
- Use agents liberally to keep the orchestrator's context window clean
- When a problem is hard, throw more compute at it — spawn agents in parallel rather than working sequentially in the orchestrator
Reason: Sub-agents are specialized experts with full tool access. Prescribing implementation limits their ability to discover better solutions. The orchestrator's context window is finite and shared across the whole session — agents get fresh context per task. Parallel dispatch solves more, faster, without accumulating context debt.