Generate competing hypotheses and collect evidence using Claude Code team mode.
npx skills add https://github.com/ClementATH/oh-my-claudecode --skill trace-clementath
Please help me install this Agent Skill. Skill: trace Source: https://github.com/ClementATH/oh-my-claudecode/tree/main/skills/trace Command: npx skills add https://github.com/ClementATH/oh-my-claudecode --skill trace-clementath
Ambiguity and conflicting signals in Claude Code runs require a structured approach to determine why results occur; this skill provides an orchestration layer that reasons with competing explanations and gathers evidence in parallel.
Provide an evidence-driven trace by restating the observation, generating hypotheses, and collecting supporting and opposing evidence using Claude's built-in team mode.
High-intent search queries and answers about installing and using this skill.
Root-cause analysis for ambiguous runtime bugs uses evidence-driven tracing to generate competing hypotheses, collect supporting and opposing evidence in parallel via team mode, and rank explanations by evidence strength.
Evidence-driven tracing evaluates hypotheses by spawning Claude's built-in team-mode lanes to gather evidence for and against each explanation simultaneously, then ranks them by evidence strength to identify the most likely root cause.
Yes, team mode applies to performance questions, configuration behavior, architecture decisions, and experiments where multiple hypotheses must be evaluated in parallel to resolve conflicting signals.
Resolving conflicting signals involves restating the observation, generating deliberately different hypotheses, collecting evidence through team-mode orchestration, and outputting a discriminating probe to quickly resolve uncertainty.
No external dependencies are required; root-cause tracing operates entirely within Claude Code's built-in team mode, using its orchestration rules to generate hypotheses and collect evidence without additional packages.
Parallel hypothesis tracing is not suited for single-cause deterministic errors where the root cause is already obvious, as the overhead of spawning team-mode lanes adds complexity without benefit.
INNERJOINTTrace causal observations to rank competing explanations for system behavior.
EvolutionAPIGenerate ranked hypotheses with evidence for ambiguous engineering observations.
Pryma-TechOrchestrate competing tracer hypotheses to explain observed Claude team-mode results.
jlawsDebug complex software bugs through sequential hypothesis testing and root-cause reporting.
