| Expert | What They Do | Example Triggers | |--------|--------------|------------------| | Architect | System design, tradeoffs, complex debugging | "How should I structure this?" / "What are the tradeoffs?" | | Plan Reviewer | Validate plans before you start | "Review this migration plan" / "Is this approach sound?" | | Scope Analyst | Catch ambiguities early | "What am I missing?" / "Clarify the scope" | | Code Reviewer | Find bugs, improve quality | "Review this PR" / "What's wrong with this?" | | Security Analyst | Vulnerabilities, threat modeling | "Is this secure?" / "Harden this endpoint" |

When Experts Help Most

• Architecture decisions — "Should I use Redis or in-memory caching?"
• Stuck debugging — After 2+ failed attempts, get a fresh perspective
• Pre-implementation — Validate your plan before writing code
• Security concerns — "Is this auth flow safe?"
• Code quality — Get a second opinion on your implementation

When NOT to Use Experts

• Simple file operations (Claude handles these directly)
• First attempt at any fix (try yourself first)
• Trivial questions (no need to delegate)

How It Works

You: "Is this authentication flow secure?"
                    ↓
Claude: [Detects security question → selects Security Analyst]
                    ↓
        ┌─────────────────────────────┐
        │  mcp__codex__codex          │
        │  → Security Analyst prompt  │
        │  → GPT analyzes your code   │
        └─────────────────────────────┘
    ...