trace

# /trace — Investigation and Root Cause Analysis Investigate unknown failures. Dispatch a trace subagent to reproduce, trace, and isolate root cause — then hand the report to `/fix`. ## When to Use - A failure exists but the cause is unknown - Stack traces or error messages don't point to an obvious defect - Multiple files or systems may be involved - Orchestrator needs a diagnosis before dispatching a fix - `/review` encounters a failure with unclear root cause and invokes `/trace` for investigation ## Flow 1. **Collect symptoms:** gather error messages, stack traces, logs, and expected vs actual behavior from the wish or reporter. 2. **Dispatch tracer:** the spawned agent IS the tracer — it performs a read-only inline investigation. Send symptoms + relevant context (files, recent changes, environment). 3. **Investigate:** the tracer autonomously reproduces, hypothesizes, traces, and isolates root cause. 4. **Signal findings:** tracer reports findings back to the leader via `genie agent send '<diagnosis summary>' --to <leader>`. 5. **Receive report:** structured diagnosis with root cause, evidence, recommended correction, and affected scope. 6. **Hand off:** pass the report to `/fix` or escalate to the orchestrator. ## Report Format ``` Root cause: <what's actually broken — file, line, condition> Evidence: <reproduction steps, traces, proof> Causal chain: <root cause → intermediate effects → observed symptom> Recommended correction: <what to change, where, why> Affected...