Skip to content
SkillModel-led962 tokens in use

strategy-red-team

Attack the load-bearing assumptions of a PRD, roadmap or strategy and get kill criteria and the cheapest test for each one.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-execution/skills/strategy-red-team
claude plugin install pm-execution@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing strategy-red-team costs

78tokens idle
962tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure25/25
  • Examples6/15
  • Output10/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

strategy-red-team acts as a sharp, fair adversary on a plan. It extracts every claim, keeps only the load-bearing ones, states the strongest version of each and then attacks that version. Each failure is written as “Fails if ___” so it can be tested.

Failure modes are ranked by impact if wrong, likelihood of being wrong and how cheap they are to test. For the three to five that survive it gives the evidence to collect this week, a kill criterion and the smallest experiment.

What You Get

  • Three to five ranked kill-assumptions
  • For each: the claim, the Fails if condition, the evidence to get this week, the kill criterion and the cheapest test
  • A What’s Well-Reasoned section listing what survives the attack
  • A What I Couldn’t Assess section for gaps in the plan
  • An optional second-model comparison on request

Common Use Cases

  • Pressure-testing a PRD before engineering starts
  • Preparing a strategy doc for executive review
  • Choosing which assumption to test first this week

What Makes It Unique

It bans strawmen, generic risk lists and invented weaknesses, and it ranks by cheapness to test so the output ends with what to do. An optional cross-model mode runs the plan through another model and flags where the two disagree.

Under The Hood

The skill is one SKILL.md of instructions with no scripts. The agent reads the plan file you provide and reasons through the claims. Only if you ask for a second opinion and another model is reachable does it send the plan to that model; the default is a single-model review that calls nothing external.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers