What problem does it solve?
Replaces guesswork with a disciplined, hypothesis-driven debugging methodology that guides engineers through a repeatable four-phase workflow for investigating and resolving bugs, including a hard-gate when three fix attempts fail.
Core Features & Use Cases
- The Four-Phase Debugging Loop: Investigate, Analyze, Hypothesize and Test, Fix, with a mandatory evaluation gate after three failed fixes.
- The Three Strikes Rule: escalates to architectural review when fixes fail thrice to prevent patching systemic issues.
- Loop Detection: circuit-breaker style safeguards that halt repeated failing attempts and surface root-cause classifications.
- Error Classification & Decision Trees: structured categorization to guide investigation, experimentation, and logging.
- Strategic Logging Guidance: minimum, purpose-driven logs at decision points and boundaries to capture reasoning and results.
- Git Bisect for Regressions: recommended practice to identify the exact commit introducing a bug.
- Escalation & Documentation Paths: clear routes for multi-tenant and architectural concerns to ensure safe handoffs.
Quick Start
Start by identifying the bug, then follow the four-phase debugging loop—Investigate, Analyze, Hypothesize and Test, Fix—and apply the three-strikes rule if fixes fail.
