debug-phase

To identify the root cause of a software bug systematically, apply the 5 Whys analysis technique to trace the issue back to its origin, classify the error by type and severity, and document the investigation in a structured error log.

The 5 Whys method is a root-cause analysis technique that helps locate the underlying cause of an error by repeatedly asking why an issue occurs, moving beyond surface symptoms to build structured reproduction steps and document the investigation.

Writing a step-by-step reproduction plan for an error log requires documenting the exact sequence of actions that trigger the failure, classifying the issue using an error severity matrix, and recording the details in error-log.md.

To create regression tests and prevent bug recurrence across projects, follow actionable guidance to design tests based on your structured reproduction steps, standardize post-mortems with checklists, and document the fixes in the error log.

Structured debugging works effectively for complex issues without specific dependencies by using an error classification framework with type and severity matrices to quickly identify and diagnose errors across any project environment.