When you hit a bug or performance issue and don't know why, this skill orchestrates parallel investigation lanes instead of letting you chase the first theory that sounds good. It spins up three tracer workers in Claude's team mode, each pursuing a deliberately different hypothesis: code path causes, config and environment issues, or measurement and assumption mismatches. Each worker gathers evidence for and against their theory, then they run a rebuttal round before ranking explanations. The output gives you the most likely cause, the critical unknown keeping competing theories alive, and the single best probe to collapse uncertainty. Treats tracing as a discipline, not just debugger output with commentary.
npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill trace