team-composition-patterns

1# Team Composition Patterns
2 
3Best practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.
4 
5## When to Use This Skill
6 
7- Deciding how many teammates to spawn for a task
8- Choosing between preset team configurations
9- Selecting the right agent type (subagent_type) for each role
10- Configuring teammate display modes (tmux, iTerm2, in-process)
11- Building custom team compositions for non-standard workflows
12 
13## Team Sizing Heuristics
14 
15| Complexity   | Team Size | When to Use                                                 |
16| ------------ | --------- | ----------------------------------------------------------- |
17| Simple       | 1-2       | Single-dimension review, isolated bug, small feature        |
18| Moderate     | 2-3       | Multi-file changes, 2-3 concerns, medium features           |
19| Complex      | 3-4       | Cross-cutting concerns, large features, deep debugging      |
20| Very Complex | 4-5       | Full-stack features, comprehensive reviews, systemic issues |
21 
22**Rule of thumb**: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.
23 
24## Preset Team Compositions
25 
26### Review Team
27 
28- **Size**: 3 reviewers
29- **Agents**: 3x `team-reviewer`
30- **Default dimensions**: security, performance, architecture
31- **Use when**: Code changes need multi-dimensional quality assessment
32 
33### Debug Team
34 
35- **Size**: 3 investigators
36…