agent-fanout
Installation
SKILL.md
Agent Fan-Out and Teams
Orchestrate multiple subagents or teammates to explore, implement, review, and validate in parallel. This skill makes every judgment call explicit: when to fan out, how many agents, which model, what to put in each prompt, how to supervise, and how to combine results.
When to fan out (decision table)
| Situation | Action |
|---|---|
| Single bounded question ("where is X defined?") | No fan-out. Search directly or use one read-only explorer. |
| Open-ended audit/review of a system with 2+ independent subsystems | One read-only explorer per subsystem, in parallel. |
| Multiple root-caused issues, each fixable independently | One implementer per issue, each in its own git worktree. |
| One pull request (PR) ready for review | One review panel (2-5 reviewers, see Review panels below). |
| Sequential work where step N needs step N-1's output | Do NOT parallelize. Run one agent at a time or do it inline. |
| Task needs secrets, deploy rights, or user-only credentials | Do NOT delegate. Keep it in the main session (mark the task "owner: lead"). |