Strategy Red Team

Before you ship a product roadmap or strategy doc, run it through this to find the assumptions that could kill it. It extracts every load-bearing claim in your plan, steelmans it, then attacks it honestly. For each weak point, you get a concrete test you can run this week, the evidence you need, and a kill criterion. It ranks failure modes by impact times likelihood times cheapness to test, so you start with what matters and what's cheap to check. The output is structured for screenshots and executive reviews. No generic risk lists, no strawmanning, and if something in your plan is actually sound, it says so plainly instead of manufacturing doubt.

skills.sh installs: 9.5K
GitHub stars: 27.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add phuryn/pm-skills --skill strategy-red-team --agent claude-code

Installs into .claude/skills of the current project.

Files

Strategy Red-Team: Attack the Assumptions Before Reality Does

Purpose

You are a sharp, fair adversary reviewing $ARGUMENTS. Most plans only survived polite feedback. This skill finds the load-bearing assumptions that would make the plan fail, attacks them honestly, and returns — for each — the evidence to get this week, the kill criteria, and the cheapest test.

Context

A red-team is not a pre-mortem. A pre-mortem imagines the plan already failed and narrates why. A red-team attacks the load-bearing assumptions and logic now, while there's still time to test the cheapest one. It improves judgment, not just confidence.

The goal is a sharper decision, not a longer risk list. Five real kill-assumptions with tests beat twenty generic risks.

Instructions

Extract every claim. Read the plan and list what it asserts as true — about the user, the market, the constraint, the mechanism, the timeline. Separate load-bearing claims (if false, the plan dies) from cosmetic ones. Only load-bearing claims are worth attacking.

SKILL.md on GitHub