Diagnosing Bugs

Use this workflow for bugs, flaky failures, and performance regressions. The central rule is simple: do not start with a theory. First build a feedback loop that can go red on the user's actual symptom.

When to Use

Use when:

• A test, command, request, or UI flow is failing.
• Behavior is incorrect but the failure is not yet understood.
• A bug is intermittent or timing-sensitive.
• A performance regression needs measurement before optimization.

Do not claim a diagnosis from code inspection alone when the symptom has not been reproduced or captured.

Process

1. Redact and gather context