adversarial-hat

Critique documents and plans to identify and prioritize weaknesses.

3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill adversarial-hat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-hat
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/adversarial-hat
Command: npx skills add https://github.com/dvy1987/agent-loom --skill adversarial-hat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies unsupported claims, hidden assumptions, and fragile solutions in documents and plans so teams avoid committing to flawed strategies or designs.

Core Features & Use Cases

  • Three-phase red team process: Diagnostic (verify claims), Creative (broaden problem framing), and Challenge (stress-test solutions and failure modes).
  • Actionable findings: Each issue is reported with the challenged claim, specific evidence or reasoning, a severity label (Critical/Significant/Minor), and explicit resolution conditions.
  • Use cases: PRD reviews, product-soul validation, design doc critique, implementation plan risk assessment, and pre-launch sanity checks.

Quick Start

Run an adversarial review on the attached PRD and return critical, significant, and minor findings with evidence and concrete resolution conditions.

Frequently Asked Questions about adversarial-hat

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

FAQPage Schema
How do I run an adversarial review on a PRD to find hidden assumptions?

To run an adversarial review, provide the document text, stated claims, and desired stakes level. The process performs a three-phase red team critique to identify unsupported claims and hidden assumptions, returning severity-tagged findings with evidence and explicit resolution conditions.

What is red team critique and when do I need it for product design documents?

Red team critique is a structured adversarial analysis used to expose and fix weaknesses before commitment. You need it for product-soul validation, design docs, or implementation plans to verify claims, stress-test solutions, and avoid committing to fragile strategies.

Can I use assumption-testing to prioritize weaknesses in an implementation plan?

Yes, you can use assumption-testing to prioritize weaknesses by supplying the implementation plan text and desired stakes level. The critique outputs severity-tagged findings—Critical, Significant, or Minor—based on evidence to help prioritize plan risks.

Does the adversarial critique process require specific document formats?

The adversarial critique process does not specify required document formats but requires the document text, stated claims or metrics, and desired stakes level as input to produce actionable findings and explicit resolution conditions.

What is the best way to stress-test failure modes in a brainstorming output?

The best way to stress-test failure modes is applying the Challenge phase of an adversarial critique. By providing the brainstorming output and claims, the process broadens problem framing and returns severity-tagged findings with concrete resolution conditions.