Pre-handoff evidence review

When it applies

The active work is done — findings drafted in findings/, notes.md complete, activity log populated — and you're about to write the report (reporting-pentest-report, reporting-bug-bounty-writeup) or hand the case to a teammate, client, or incident stakeholder. This is a read-only audit of engagements/<target>/: it never touches the target and never adds new testing. If a check fails, go back to the owning skill — don't patch the report to hide the gap.

Why it works

Reports get killed in review for the same few reasons: a finding with no reproducible proof, a lead silently dropped, scope ambiguity, or an artifact that no longer matches its hash. A structured pass over the package catches these while they're still cheap to fix and produces a handoff another human can defend without you in the room.

Method

Work the package top to bottom; every failure is a blocker until fixed or explicitly waived with a written reason.