systematic-debugging

Root cause analysis requires a systematic four-phase framework: investigate what's happening, analyze patterns across failures, test hypotheses against evidence, then implement the fix. This Skill guides you through each phase to ensure you diagnose the actual problem, not just treat visible symptoms, preventing wasted time and new bugs from incorrect patches.

Systematic debugging applies a structured process across test failures, production bugs, integration issues, and performance problems. It mandates diagnostic instrumentation, evidence-based verification through failing test cases, and explicit anti-patterns that resist shortcuts even under time pressure, ensuring thorough root-cause exploration before any fix.

Quick fixes often treat symptoms rather than root causes, introducing new bugs. This Skill enforces a four-phase framework with explicit rules against rationalization and shortcuts, requiring you to investigate thoroughly, test hypotheses with evidence, and verify fixes with failing test cases before deployment.

Yes. Systematic debugging applies to modern software stacks, multi-component architectures, test failures, integration issues, and performance problems. The framework adapts to different technologies by focusing on diagnostic instrumentation and evidence-based hypothesis testing rather than stack-specific tools.

Fixes that don't address root causes often fail in different contexts. Systematic debugging requires diagnostic instrumentation across your multi-component architecture, evidence-based verification through failing test cases, and hypothesis testing that ensures your fix works across environments, not just locally.

Time pressure is exactly when root-cause analysis matters most—quick patches create cascading failures. This Skill includes explicit anti-rationalization rules that counter excuses for shortcuts, showing why systematic debugging saves time overall by preventing regressions and follow-up firefighting.