Earlier quoted context omitted.
Right - don’t make subagents for the different roles, make them to manage context for token heavy tasks. A backend developer subagent is going to do the job ok, but then the supervisor agent will be missing useful context about what’s been done and will go off the rails. The ideal sub agent is one that can take a simple question, use up massive amounts of tokens answering it, and then return a simple answer, dropping…
This is my experience too. Make agents for tasks, not roles. I've seen this for coding agents using spec-driven development for example. You can try to divide agents into lots of different roles that roughly correspond to human job positions, like for example BMad does, or you can simply make each agent do a task and have a template for the task. Like make an implementation plan using a template for an implementation…
Re: How to use Claude Code subagents to parallelize development
#131FYI: BMAD has roles, but to those are attached other document the persona should be using (checklist, template, tasks, etc ...).