avad-debug

What problem does it solve?

Systematic debugging with a formal root-cause framework reduces guesswork and accelerates reliable fixes by enforcing a structured, phased approach.

Core Features & Use Cases

• Phase 1: Root Cause Investigation — collect symptoms, reproduce the bug, and trace the code path.
• Phase 2: Pattern Analysis — identify problem patterns like race conditions, nil/null propagation, or integration failures.
• Phase 3: Hypothesis Testing — generate evidence-backed hypotheses and validate them with lightweight checks.
• Phase 4: Implementation — fix the root cause with minimal changes and add regression tests.
• Phase 5: Verification & Report — reproduce the original scenario and deliver a structured debug report.
• Scope Lock considerations — optional boundary controls to prevent scope creep during debugging sessions.
• Use Case: Incident response, bug triage, and post-mortem debugging across languages and stacks.

Quick Start

Begin a debugging session by collecting symptoms, reproducing the bug, and then proceed through the five phases to identify the root cause before implementing a fix.