team-debug

Root-cause debugging traces symptoms back to their origin by documenting evidence and enforcing investigation before any fixes are applied. This methodology reduces regression risk and speeds up resolution by verifying the actual cause.

Systematic debugging uses pattern analysis across the codebase to identify recurring failure modes, guiding holistic fixes rather than isolated patches. This approach surfaces design-level constraints through architecture checks when necessary.

Reproduction tests and a validation workflow verify fixes by confirming the root cause before implementation. This ensures the original issue is resolved without introducing regressions or new issues.

An escalation protocol is needed during bug triage when architecture checks surface design-level constraints that exceed standard remediation scope. It ensures safe, repeatable remediation by elevating complex systemic issues.

A structured debugging workflow for team-build failures uses a five-phase process starting with root-cause investigation, followed by evidence documentation, reproduction tests, verified fixes, and pattern analysis.

Root-cause debugging integrates with safety and quality hooks to ensure structured phases and rationale documentation are enforced. This integration provides repeatable remediation and validation throughout the fixing process.