adversarial-reviewlisted

# Adversarial Review Use this skill to stress-test a draft before it reaches real reviewers. It spawns a small swarm of specialized persona subagents in parallel, each attacking the manuscript from one angle, then synthesizes the critiques into a prioritized fix list. This is the opposite of a friendly read-through. The goal is to surface desk-reject-level problems, unsupported claims, weak statistics, and citation hallucinations *before* submission — not to reassure the author. ## When to use - Pre-submission audit for a journal (PRX, JCAP, JOSS, etc.) or conference. - Internal circulation of a research report or technical memo. - Response drafting for a revise-and-resubmit where the author wants to predict reviewer pushback. - Any draft the user wants "torn apart" or "reviewed hard." If the user wants a friendly copy-edit pass, this is the wrong skill — suggest a plain editing request instead. ## Inputs to confirm Ask only for what is missing: - path to the draft (default: `report.md` in the current directory) - journal or venue the draft targets (affects the Journal Editor persona) - any sections the user wants emphasized or skipped - whether figures live alongside the draft and where (`plots/`, `figures/`, etc.) - whether a bibliography file or a references section should be audited - whether Korean translation of the final summary is expected If nothing is specified, default to: - draft: `report.md` in CWD - venue: "general physics/ML journal" (Journal Editor per