red-team

# Red Team ## Overview <!-- CANONICAL: shared/dispatch-convention.md --> All subagent dispatches use disk-mediated dispatch. See `shared/dispatch-convention.md` for the full protocol. Adversarial review of any artifact. Dispatches a Devil's Advocate subagent to attack the work, fixes findings, then dispatches a FRESH Devil's Advocate to attack again. Iterates until clean or stagnation is detected. **Core principle:** Fresh eyes every round. No anchoring, no confirmation bias. **Announce at start:** "I'm using the red-team skill to adversarially review this artifact." ## When to Use - After a design doc is finalized (before planning) - After an implementation plan passes review (before execution) - After implementation is complete (before finishing) - Anytime you want adversarial review of any artifact - When the build pipeline calls for red-teaming ## The Iterative Loop ```dot digraph red_team_loop { "Dispatch FRESH Devil's Advocate" -> "Reviewer returns findings"; "Reviewer returns findings" -> "No Fatal/Significant issues" [label="clean"]; "No Fatal/Significant issues" -> "Artifact approved -- proceed"; "Reviewer returns findings" -> "Fatal/Significant issues found"; "Fatal/Significant issues found" -> "Dispatch fix agent"; "Dispatch fix agent" -> "Score issues (Fatal=3, Significant=1)"; "Score issues (Fatal=3, Significant=1)" -> "Compare weighted score to prior round"; "Compare weighted score to prior round" -> "Dispatch FRESH Devil's Advocate" [la...