verify-first-debugging

A verify-first debugging framework systematically isolates root causes by enforcing a six-phase workflow that requires verified facts and evidence collection before applying any fixes, ensuring traceable and auditable remediation.

To debug flaky software bugs without assumptions, use an orchestrated phase-management workflow that reproduces the expected behavior, verifies component relationships, and identifies the root cause before applying a durable, rollback-safe fix.

Structure a debugging workflow by dividing the cycle into six distinct phases: reproduce and define expected behavior, locate affected components, verify relationships, verify prerequisites, identify the root cause, and fix at the root.

Verify-first debugging works for complex UI bugs with missing data by utilizing phase-specific replan logic and rollback-safe workflows, ensuring you confirm exact reproduction steps and narrow down responsible components safely.

The best way to prevent superficial patches during software remediation is to enforce risk-aware root-cause fixes using an orchestrator that requires phase artefacts and success criteria validation before advancing to the final repair.

You should use phase management for root-cause analysis because orchestrated SubAgents and structured phase handoffs produce a rigorous evidence chain, preventing premature fixes and ensuring the actual fault is addressed.