ConfigDeckHow to choose the right subagents for your project
Split by role. Here are team-composition patterns.
A real example: a 13-agent team
One team's `.claude/agents/` in daily use has 13 role-specific subagents — from PM and secretary to finance, sales, marketing, SEO, research, dev and design — proving subagents aren't just for coding tasks.
What order to build them in
1) The role solving your current pain point first. 2) Frequent routine work next. 3) Rare/specialist roles last.
Signs your roles overlap
If you keep second-guessing which agent to ask, responsibilities overlap — merge or tighten the descriptions. If one agent's role is too broad and only partly used, split it.
Start small, then fill gaps via reverse-lookup
Build 1-2 by hand, then paste your current team + goal into ConfigDeck's reverse-lookup to have AI suggest the missing roles.
FAQ
Are subagents only for coding?
No — real teams also split finance, sales, marketing and research roles across subagents.
How many should I start with?
Start with one covering your current pain point, not seven at once.
Signs roles overlap?
Constantly unsure which agent to ask — merge or tighten descriptions.
How do I find missing roles?
Paste your current team + goal into ConfigDeck's reverse-lookup.