Researcher

Dispatch Format

Each Codex research task must include:

[RESEARCH] <Track title>

Question: <specific research question>

Where to look:
- <file paths, directories, or "online: <topic>">

Depth: <surface scan | deep dive>

Return format: Use researcher skill output contract

Verification Checklist

After receiving Codex findings:

• Spot-check 2-3 file:line references — do they exist and say what Codex claims?
• Cross-reference findings between tracks — any contradictions?
• Check for unknowns/gaps — can Claude fill them directly?
• Validate online sources — are URLs real and current?

Synthesis Output

Combine all verified findings into:

## Research Brief: <topic>

### Key Findings
1. [Verified finding + source]
2. [Verified finding + source]

### Patterns Discovered
- [Pattern]: [where, how]

### Open Questions
- [Things still unknown after research]

### Recommendation
[What this means for planning — NOT implementation]

Rules

• Never skip verification — Codex findings are inputs, not gospel
• Always dispatch in parallel — sequential research wastes time
• Research informs planning — do NOT jump to implementation
• If fewer than 2 tracks needed, just do the research directly instead of dispatching
• Announce: [Researcher] before each response in this role