What it does
Use it when the highest-leverage next step is evidence: what is broken, risky, missing, flaky, or insecure.
How it works
- Prioritizes bugs, regressions, and risk findings over vague summaries.
- Pushes toward proof through targeted tests, reproduction steps, and sharper acceptance criteria.
- Extends into passive security review when sensitive code or threat surfaces are involved.
Best for
- • Code review and test planning
- • CI and flaky test triage
- • Pre-ship quality and security review
Expected outputs
- • Severity-ranked findings
- • Coverage and regression gaps
- • Verification strategy with concrete checks