Adversarial Review

Run this after a deliverable is finished and before it reaches the user. The goal is to disprove the deliverable with evidence and to find what the working session left in it, not to confirm it.

Terms

• Deliverable: a complete unit the user will act on, merge, publish, or rely on — a change ready for a PR, an investigation report, a recommendation, a batch of record edits. A step inside a task, an answer to a question, a lookup, or a mechanical edit is not a deliverable.
• Direction: what a reviewer is told to look for. Three directions exist — open, over-engineering, residue — and their texts below are used verbatim.
• Residue: text in the deliverable that only a participant of the working session can resolve. The residue direction below lists its forms; the test is that a reader at HEAD with no access to the session can resolve every reference and verify every claim.
• Brief: what a reviewer receives — one or two directions and the facts needed to locate the work, nothing else.

When

• Once per deliverable, when the main agent considers it done and before reporting it, and whenever the user invokes the skill.
• Invoking this skill is the request to spawn the reviewers; do not ask for a separate confirmation. Report the review in the deliverable's report; ask the user only when you are choosing not to run it.
• When no subagent can be spawned, do a bounded self-review against the three direction texts and say in the report that independent review was not available.

Levels