systematic-debugging

Root-cause debugging enforces a mandatory investigation phase to identify the actual origin of a bug before applying any remedy. This systematic approach prevents recurring issues and reduces rework caused by superficial symptom patches.

Debug production incidents by following a four-phase workflow starting with root-cause investigation, then pattern analysis, hypothesis testing, and implementation. Built-in anti-patterns and defensive checks help resist rationalization and time pressure during resolution.

Common debugging anti-patterns include skipping root-cause investigation and applying immediate symptom fixes. This Skill enforces a mandatory Phase 1 investigation and defense-in-depth guidance to resist rationalization and guesswork under time pressure.

Systematic debugging applies across development, staging, and production environments. The four-phase workflow ensures consistent root-cause analysis regardless of the environment, making it suitable for academic exercises and production incidents alike.

The best way to stop symptom patching is enforcing a strict four-phase workflow where Phase 1 root-cause investigation must be completed before any fixes are proposed. Defense-in-depth guidance and anti-pattern checks prevent premature implementation.