adversarial-review

Stress-tests plans and proposals through pre-mortem analysis and seven structured critique lenses.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill adversarial-review-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/adversarial-review
Command: npx skills add https://github.com/Claudfather/clauDNA --skill adversarial-review-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and design proposals often contain hidden assumptions, unexamined failure modes, and blind spots that only surface after resources are committed. This Skill stress-tests any plan before execution, surfacing blockers, risks, and gaps while changes are still cheap. ## Core Features & Use Cases - Structured Multi-Lens Review: Applies seven lenses — first principles, gaps and blind spots, edge cases and scale, alternatives, implementation risk, press release test, and counter-plan — plus pre-mortem and Murphyjitsu calibration. - Multi-Reviewer Dispatch Mode: Spawns parallel critic subagents (Architect, Skeptic, Operator, User, Counter-Planner) with anti-groupthink guards like the 10th Man Rule for major initiatives. - Classified Findings Output: Produces a structured review with Blockers, Risks, Gaps, Questions, an assumption map, and a summary table, delivered in chat or as GitHub Issues. - Use Case: Before committing a team to a six-week migration plan, run an adversarial review to surface the unstated dependency on a legacy service and the missing rollback strategy, then revise the plan before implementation starts. ## Quick Start Ask the AI to run an adversarial review on your plan document, for example by pointing it at a plan file path and requesting a stress-test of its assumptions and failure modes.

Frequently Asked Questions about adversarial-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a project plan before implementation?

Run an adversarial review on the plan document. It applies a pre-mortem, seven structured critique lenses, and a Murphyjitsu calibration loop to surface blockers, risks, and unstated assumptions, then classifies each finding by severity with suggested fixes.

What is the difference between adversarial review and code review?

Adversarial review evaluates whether a plan should be built at all and whether its approach is sound, while code review checks whether written code is correct. This skill reviews plans and proposals, though it verifies claims against the actual codebase with file:line citations.

When should I use dispatch mode versus single review mode?

Use single interactive mode for smaller plans. Use --dispatch mode for initiatives taking more than a week or affecting multiple systems — it spawns five parallel specialist reviewers and adds anti-groupthink guards like the 10th Man Rule.

Can adversarial review findings be published to GitHub?

Yes. Passing --output github creates one umbrella issue containing the full review plus individual issues for each Blocker and critical-severity Risk. The default --output session presents findings directly in chat.

What happens if the review finds no problems with a plan?

A zero-finding result triggers an early-agreement check that forces a second pass explicitly hunting for at least one credible Blocker. If none exists even then, that is recorded as a genuine signal of plan strength rather than a rubber stamp.