strategy-red-team

Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions with ranked failure modes.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill strategy-red-team-choi-keith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategy-red-team
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-execution/skills/strategy-red-team
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill strategy-red-team-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Most plans only receive polite feedback, so critical assumptions go untested until reality breaks them. This Skill adversarially reviews a PRD, roadmap, or strategy to find the claims that would kill the plan if false, and tells you exactly what evidence to gather this week. ## Core Features & Use Cases - Assumption Extraction & Steelmanning: Lists every claim in the plan, separates load-bearing assertions from trivial ones, then attacks the strongest version of each rather than strawmen. - Ranked Failure Modes: Scores each failure mode by impact × likelihood × test cost, so the cheapest high-impact test surfaces first. - Actionable Output: For each surviving kill-assumption, returns the failure condition, evidence to gather this week, a kill criterion, and the cheapest test, plus explicit notes on what is well-reasoned and what could not be assessed. - Use Case: Before an executive review of a new product roadmap, run the plan through this Skill to get 3-5 ranked kill-assumptions with concrete validation experiments instead of a generic risk list. ## Quick Start Ask the AI to red-team your attached PRD or strategy document and return the top kill-assumptions ranked with cheapest tests and kill criteria.

Frequently Asked Questions about strategy-red-team

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

FAQPage Schema
How do I stress-test a product strategy or PRD before launch?

Red-team the plan by extracting every claim it asserts, isolating the load-bearing assumptions, and attacking the strongest version of each. Rank failure modes by impact, likelihood, and test cost, then run the cheapest test on the top-ranked assumption this week.

What is the difference between a red team and a pre-mortem?

A pre-mortem assumes the plan already failed and works backward to find causes. A red team attacks the plan's key assumptions and logic in the present, while there is still time to run the cheapest test and change course.

How do I prioritize which assumptions to test first?

Score each failure mode on three factors: impact if wrong, likelihood of being wrong, and cost to test. The assumption with high impact, high likelihood, and low test cost should be tested this week, ahead of everything else.

Can I get a second opinion from another AI model on my plan?

Yes, the Skill supports an optional cross-model mode where the same plan is run through another model such as Codex or Gemini, and disagreements between the two are flagged. This is off by default and only runs when requested.

When should I not use red-team analysis on a plan?

Avoid it when you only want a generic risk checklist, since every output must target the specific plan. It is also a poor fit if the plan lacks enough substance to extract concrete, falsifiable claims.