← ClaudeAtlas

pm-red-teamlisted

Adversarially re-review a PM artifact, recommendation, or AI-generated critique that already exists. Use as a second pass after another skill (pm-evaluator, pm-prd-drafter, pm-decision-coach, pm-value-hypothesis-tester) has produced output, or on any external AI output the user wants pressure-tested before deferring to it. Plays the role of a hostile exec, skeptical board member, or competing PM — looking for what the first pass missed, what bias it brought, and what would not survive a real review. Returns the three load-bearing holes, what's already strong enough to keep, and the specific re-writes that would close the gaps.
kalyvask/pm-evaluation-framework · ★ 0 · Testing & QA · score 72
Install: claude install-skill kalyvask/pm-evaluation-framework
# PM red team Runs an adversarial second pass on something that has already been written or critiqued. The goal is not to be contrarian — it's to surface the parts of the analysis that wouldn't survive a hostile reviewer (an exec, a board member, a sharp peer PM, a competitor strategist). Adapted from the chief-of-staff pattern of critically evaluating AI output rather than deferring to it. The skill is opinionated. It will disagree with the prior pass when it has reason to. It will keep what's strong. It will not generate noise just to look productive. ## When to use Use this when: - A primary PM skill (`pm-evaluator`, `pm-prd-drafter`, `pm-decision-coach`, `pm-value-hypothesis-tester`, `pm-metrics-critic`, `pm-launch-reviewer`) has produced an evaluation or draft, and the user wants it pressure-tested before sending up the chain - The user has pasted an **external AI output** (ChatGPT, Gemini, another Claude session) and wants it challenged rather than trusted - The user has written their own draft and wants an adversarial read before circulating - A recommendation feels right but the user wants to make sure they're not just being told what they wanted to hear Don't use this when: - No prior analysis exists yet — run the primary skill first, then chain to this - The user wants the artifact written from scratch — use `pm-prd-drafter` or `pm-decision-coach` - The user wants emotional support — they want adversarial pushback, not validation, but make sure that's actually