What problem does it solve?
This Skill helps you diagnose hard-to-reproduce bugs by turning vague symptoms into competing, testable hypotheses backed by concrete evidence.
Core Features & Use Cases
- Competitive hypothesis debugging: structures the investigation into ranked candidate root causes that can be disproven.
- Evidence strength hierarchy: prioritizes direct reproduction and primary sources (code/log/measurements) over weaker inference.
- Parallel exploration workflow: runs distinct investigation lanes in parallel to quickly narrow the best explanation.
- Safety-first diagnostic contract: enforces a “Trace Contract” (observation, hypotheses, evidence for/against, best explanation, unknowns, next probe) so conclusions stay evidence-grounded.
Use case examples
- Intermittent production errors: occasional 500s that only happen under certain conditions.
- Environment-specific failures: passes locally but fails in CI or staging.
- Performance regressions: latency increases after a deployment with unclear cause.
Quick Start
Run the trace skill with a clear symptom statement like: trace “After login, intermittently 500 errors happen in production only.”