Agents & Subagents

Use specialized agents for complex work without losing coordination.

When subagents help

Use a subagent when specialization genuinely reduces complexity: security review, testing, repository exploration, research, database architecture, or documentation.

Example team

Orchestrator
├── Database Architect → schema, indexes, migrations
├── Backend Developer → API and business logic
├── Frontend Developer → responsive interface
├── Security Reviewer → auth, validation, injection checks
└── Tester → regression and acceptance tests

Output contracts

Each agent should return a defined deliverable. The orchestrator reconciles disagreements and performs final validation. More agents are not automatically better.

Finish this level

Create an account to track progress, save notes, bookmarks and scores.

Create Account Login