Generate competing hypotheses and rank evidence to triage ambiguous observations.
npx skills add https://github.com/sehoon787/my-claude --skill trace-sehoon787
Please help me install this Agent Skill. Skill: trace Source: https://github.com/sehoon787/my-claude/tree/main/skills/omc/trace Command: npx skills add https://github.com/sehoon787/my-claude --skill trace-sehoon787
Ambiguity in observed results and complex root causes require evaluating multiple explanations in parallel; this skill provides a structured lane to generate competing hypotheses, gather evidence, and rank explanations.
Provide a trace run for a given observation by generating three distinct hypotheses, collecting evidence for and against each, and returning a ranked synthesis with the best discriminating probe.
High-intent search queries and answers about installing and using this skill.
Root-cause analysis for runtime bugs and performance anomalies requires generating competing hypotheses, collecting evidence for and against each, and returning a ranked synthesis with a discriminating probe to resolve the issue.
Triaging multiple architectural explanations involves spawning parallel tracer lanes to explore distinct hypotheses, comparing supporting and refuting artifacts, and ranking explanations by evidence weight to identify the most likely cause.
Team-mode tracing automatically spawns multiple dedicated lanes to explore distinct hypotheses in parallel, collecting explicit evidence for and against each before synthesizing a final ranked conclusion with a critical unknown.
Yes, the structured tracing workflow triages ambiguous performance anomalies by starting from observation, generating three distinct hypotheses, and then systematically collecting evidence for and against each to determine the most likely cause.
A ranked synthesis for ambiguous observations includes the most likely explanation determined by evidence weight, a critical unknown that remains unresolved, and a discriminating probe to accelerate final resolution.
Use parallel hypothesis tracing when runtime bugs, performance anomalies, or architectural questions present multiple valid explanations that must be weighed simultaneously with explicit evidence for and against each hypothesis.
OutlineDrivenIsolate root causes with a hypothesis-driven minimal-repro workflow.
pextacyAnalyzes architecture, bugs, dependencies across files, logs, and runtime traces to identify root causes.
OliverOuyangOrchestrate parallel hypothesis tracing and evidence collection for causal failure analysis.
jlawsDebug complex software bugs through sequential hypothesis testing and root-cause reporting.
