rigorous-data-audit
Rigorous Data Audit
Procedure for auditing mods where a bug equals lost player progression. Built from a real failure: six parallel Opus reasoning agents reviewed LF_VStorage 1.4.6 from independent angles and signed off as "release-safe" — an external implementer-grade audit then found 12 VULNs (P0–P3) the agents missed. This skill encodes the lessons.
A second failure refined it further: a loose application of this skill's
"parallel agents + consolidation" shape — pointed at fact-checking a corpus —
produced an audit that was ~55% confabulated, because there was no
adversarial verification step between "agents reported it" and "acting on it".
Step 3 below exists because of that. See postmortem.md for the case.
Read references/why-this-skill-exists.md for the full retrospective if you
want the original case study.