agent-orchestration
Installation
SKILL.md
Agent Orchestration
Agent orchestration is the design of systems where multiple specialized agents work together to complete a task no single agent could handle well alone. Each agent owns one job. The orchestration layer decides which agent runs, when, and what context it receives.
The principle: one agent, one job. An agent that researches accounts, writes emails, scores leads, and updates the CRM is not an agent. It's a monolith with an LLM inside. It will be mediocre at all four tasks.
When to Use Multi-Agent vs Single Agent
| Scenario | Use single agent | Use multi-agent |
|---|---|---|
| Task is one step with clear input/output | Yes | No |
| Task requires 2+ distinct skill sets | No | Yes |
| Output quality varies by subtask | No | Yes (specialize each) |
| Task has branching logic (if X do Y, else Z) | Maybe | Yes (router + specialists) |
| Task requires human review at intermediate steps | No | Yes (pause between agents) |
| Task operates on different data at different stages | No | Yes (each agent gets relevant context) |
Rule of thumb: If you're writing one system prompt longer than 2,000 words to cover multiple distinct tasks, split into agents.