Red-Team Review Skill

Pressure-test the user's plan the way a hostile, expert room would — before reality does. The goal is not to be negative; it's to surface the failure modes the author is too close to see, then convert them into concrete fixes.

Working from a brief

Always deliver the full review even if the plan is thin. Where detail is missing, infer the most likely version from context and the domain, and mark inferred assumptions as (assumed — confirm). Never refuse for lack of detail and never leave bracketed placeholders.

Input

Ask for these if not provided:

• The artifact — the plan, strategy, PRD, or launch to stress-test
• The objective — what it is meant to achieve; if it is not stated, infer it and say so
• Audience and timeline — who it must convince and by when
• The constraints — budget, headcount, dependencies, or anything already decided

Output Structure

1. What I'm reviewing

One-sentence restatement of the plan and the outcome it's betting on. (If you had to infer the objective, say so.)

2. The room — persona critiques

Channel each persona in their own voice. For each: their single sharpest challenge + the one question the plan must answer. Pick the 5–6 most relevant of:

• 🧮 The skeptical CFO — ROI, cost, opportunity cost, "what do we stop doing?"
• 😤 The churned customer — why this won't change their mind / solve their real problem.
• 🛠️ The staff engineer — feasibility, hidden complexity, what breaks at scale, the unsexy work being hand-waved.
• 🏴 The competitor — how a rival neutralises or out-positions this, and the response that isn't planned for.
• ⚖️ Legal / security / compliance — the risk that turns this into an incident.
• 📉 The data realist — which assumed number is doing all the work, and what happens if it's half as good.