trace

Trace ambiguous causal questions to identify the most likely explanation.

Updated May 20, 2026
One-click install
npx skills add https://github.com/xdkp/oh-my-claudecode --skill trace-xdkp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/xdkp/oh-my-claudecode/tree/main/skills/trace
Command: npx skills add https://github.com/xdkp/oh-my-claudecode --skill trace-xdkp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you explain the root cause of an observed outcome by turning ambiguity into evidence-backed, competing explanations.

Core Features & Use Cases

  • Evidence-driven tracing lane orchestration: Runs multiple tracer lanes to explore different hypotheses instead of converging too early.
  • Structured uncertainty handling: Forces explicit tracking of observation, hypotheses, evidence for/against, the current best explanation, and the critical unknown.
  • Discriminating next probe: Recommends the highest-value probe that would collapse uncertainty fastest, including a rebuttal round between top hypotheses.

Quick Start

Use /oh-my-claudecode:trace to trace why your system produced a surprising result by gathering competing causal explanations and the single best next probe.

Frequently Asked Questions about trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a performance regression when multiple causes are possible?

Root cause analysis for performance regressions uses evidence-driven tracing lanes to explore competing hypotheses, rank them with explicit evidence, and identify the discriminating probe that collapses uncertainty fastest.

What is the best way to debug an ambiguous system failure with conflicting evidence?

Debugging ambiguous failures requires structured uncertainty handling that tracks observations, evidence for and against hypotheses, and applies strong falsification rules to converge on the most likely explanation.

How do you compare competing causal explanations during architecture post-mortem analysis?

Architecture mortem analysis compares competing causes by running multiple tracer lanes, applying explicit evidence for and against each hypothesis, and synthesizing a final ranked explanation with a critical unknown.

Can I use team-mode orchestration to trace why my system produced a surprising result?

Team-mode orchestration with three tracer lanes traces surprising results by exploring different hypotheses simultaneously, preventing early convergence, and running a rebuttal round between top hypotheses.

When do I need hypothesis ranking and falsification rules for tracing system behavior?

Hypothesis ranking and falsification rules are needed when tracing ambiguous, evidence-heavy questions where multiple competing causes must be compared and separated based on observed evidence.

What are the limitations of tracing ambiguous causal questions without a discriminating probe?

Without a discriminating probe, tracing ambiguous causal questions risks prolonged uncertainty because no single highest-value action is recommended to collapse competing hypotheses into a confirmed root cause.