trace

# trace — Investigation and Root Cause Analysis **Runtime syntax:** invoke the plugin copy through the active runtime's owner-qualified skill selector; use a bare selector only when intentionally selecting a user-tier copy (a separately installed personal copy; Genie no longer seeds this tier). Cross-skill prose below uses bare names as portable semantic routes; the orchestrator resolves the selector for the active runtime. Investigate unknown failures: dispatch a trace subagent to reproduce, trace, and isolate root cause, then hand the report to `fix`. The deliverable is findings only — report and stop; never apply fixes, however obvious. ## 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 - `review` hit a failure with unclear root cause and needs a diagnosis before `fix` ## Flow 1. **Collect symptoms:** error messages, stack traces, logs, and expected vs actual behavior from the wish or reporter. 2. **Dispatch tracer:** native delegation surface → trace subagent, briefed with the symptoms, relevant context (files, recent changes, environment), and read-only stop conditions (see Dispatch). 3. **Investigate:** the tracer reproduces, hypothesizes, traces, and isolates root cause autonomously. 4. **Receive report:** the tracer's final message is the diagnosis (format below); the native team notifies you on completion — no polling. 5. **Hand off:** pass the re...