Claude Code Agent Teams Can Spawn Agents. It Just Doesn't Know Which Ones to Use.
Claude Code's Agent Teams feature is genuinely impressive. You type a complex prompt, it spawns subagents, they work in parallel, each with its own context window. The architecture is there. But th...

Source: DEV Community
Claude Code's Agent Teams feature is genuinely impressive. You type a complex prompt, it spawns subagents, they work in parallel, each with its own context window. The architecture is there. But there's a gap nobody talks about. Agent Teams doesn't know which agents to use. It doesn't know that a game project needs a game designer, a physics engineer, and a QA specialist. It doesn't know that a SaaS dashboard needs a frontend dev, a backend architect, and someone who understands Stripe webhooks. It spawns blank subagents with no identity, no rules, no specialization. You're supposed to define them yourself. Every time. With --agents JSON. For every project. I built the missing piece. 144 Agents, One Command npx agentcrow init That's it. This installs 144 specialized agent definitions into your project โ 9 hand-crafted builtin agents with strict MUST/MUST NOT rules, plus 135 community agents from agency-agents covering 15 divisions: engineering, game dev, design, marketing, testing, Dev