Трассировка причин через конкурирующие гипотезы

★ 8.5 · vibe-coding

trace is a Claude Code skill that orchestrates competing tracer hypotheses to explain why an observed result happened, driven strictly by evidence rather than jumping straight to a fix. It uses Claude's built-in team mode: the lead restates the observation, spawns three parallel tracer lanes by default — code-path cause, config/environment cause, and measurement/assumption mismatch cause — runs a rebuttal round between the top hypotheses, and merges findings into a ranked synthesis with an explicit critical unknown and a discriminating probe. Every hypothesis is actively falsified: evidence for and against each lane is collected and weighted according to a ranked hierarchy from controlled reproductions down to speculation. The skill is built for ambiguous, evidence-heavy causal questions such as runtime regressions, latency issues, architecture postmortems, and experimental result tracing, where premature convergence on a single explanation would be costly.