Good Subagent Roles
Useful roles include researcher, implementation agent, test fixer, reviewer, and migration planner.
Example Brief
Give each subagent a clear scope and expected artifact.
Role: reviewer Scope: inspect auth changes only Output: findings with file and line references
Common Mistakes
Ambiguous roles create duplicated work.
- Define inputs and outputs.
- Keep one owner for final integration.
- Use tests as the shared truth.
FAQ
Are subagents always faster?
No. They help when work can be split cleanly.
What should the main agent do?
Coordinate scope, integrate results, and verify the final state.
Can subagents review each other?
Yes, especially on higher-risk migrations or broad refactors.