Decision matrix for choosing the right subagent_type when spawning teammates.
Decision Matrix
Does the teammate need a specialized AgentTeams role?
├── YES → Which role?
│ ├── Team coordination → agent-teams:team-lead
│ ├── Feature building → agent-teams:team-implementer
│ ├── Code review → agent-teams:team-reviewer
│ └── Bug investigation → agent-teams:team-debugger
└── NO → Does it need to modify files?
├── YES → general-purpose
└── NO → Does it need deep codebase exploration?
├── YES → Explore
└── NO → Plan (for architecture/design tasks)
Agent Type Comparison
Agent Type
Can Read
Can Write
Can Edit
Can Bash
Team Tools
Specialized
general-purpose
Yes
Yes
Yes
Yes
No
No
Explore
Yes
No
No
No
No
Search/explore
Plan
Yes
No
No
No
No
Architecture
agent-teams:team-lead
Yes
No
No
Yes
Yes
Team orchestration
agent-teams:team-reviewer
Yes
No
No
Yes
Yes
Code review
agent-teams:team-debugger
Yes
No
No
Yes
Yes
Bug investigation
agent-teams:team-implementer
Yes
Yes
Yes
Yes
Yes
Feature building
Common Mistakes
Mistake
Why It Fails
Correct Choice
Using Explore for implementation
Cannot write/edit files
general-purpose or team-implementer
Using Plan for coding tasks
Cannot write/edit files
general-purpose or team-implementer
Using general-purpose for reviews
No review structure/checklists
team-reviewer
Using team-implementer for research
Has tools but wrong focus
Explore or Plan
When to Use Each
general-purpose
One-off tasks that don't fit specialized roles
Tasks requiring unique tool combinations
Ad-hoc scripting or automation
Explore
Codebase research and analysis
Finding files, patterns, or dependencies
Understanding architecture before planning
Plan
Designing implementation approaches
Creating task decompositions
Architecture review (read-only)
team-lead
Coordinating multiple teammates
Decomposing work and managing tasks
Synthesizing results from parallel work
team-reviewer
Focused code review on a specific dimension
Producing structured findings with severity ratings