PM Skills 2.0: Red-Team Your Roadmap, Then Check the Code Before You Ship
68 free Claude skills, 42 commands, 9 plugins. This release adds a new /red-team-prd command and the AI Shipping Kit: a way to document, audit, and ship AI-built apps with human sign-off.
Most PRDs only survive polite feedback.
You write the plan, you share it, people nod. The assumption that sinks it never gets named until launch.
So I built a command that names it first.
Paste a roadmap, a PRD, or a one-line bet into Claude. You get back the riskiest assumptions, ranked by what would hurt most, what is most likely to be wrong, and what is cheapest to test this week.
The impolite questions, before the market asks them.
It shipped today in PM Skills 2.0, the free, MIT-licensed marketplace 12,000 of you have starred on GitHub.
This is the biggest update since the March launch:
68 skills
42 commands
9 plugins
one new AI Shipping Kit
one new red-team command for PRDs, roadmaps, and strategy
1. What PM Skills Actually Is
Generic Claude gives you text. PM Skills gives you structure.
Ask a raw model to “prioritize this backlog” and you get a confident paragraph. Ask it with the prioritization-frameworks skill loaded and it runs the actual framework, with the trade-offs named and the math shown.
The difference is not the model. It is the judgment encoded in the skill.
Each skill turns a proven PM method into a reusable workflow: discovery, assumption mapping, prioritization, strategy, pricing, GTM, execution, analytics, and now AI shipping.
There are three pieces:
Skills give Claude a method or framework. They load automatically when the work matches.
Commands are slash workflows you trigger directly.
/discoverchains four skills: brainstorm ideas, identify assumptions, prioritize assumptions, and design experiments.Plugins group related skills and commands by PM domain. Installing the marketplace gives you all 9 at once in Cowork.
The full catalog lives in the GitHub README. For this release, two plugins changed.
pm-execution was updated with one new skill, strategy-red-team, and one new command, /red-team-prd.
pm-ai-shipping is new: two skills, five commands, and a workflow for turning an AI-built repo into something a human can review.
For PMs: you do not have to learn the catalog. Install it once, then work normally. The right skills surface when the task matches.
2. The New Command: /red-team-prd
This is the one to try first, because you can feel it in thirty seconds.
/pre-mortem imagines the plan already failed and narrates why. /red-team-prd does the opposite: it attacks the live assumptions now, while you can still change them, and hands you the cheapest test for each.
Here is what that looks like on a one-line bet:
You type: /red-team-prd Prioritize AI onboarding, activation is our bottleneck
You get back:
Claim: Activation is the constraint on growth.
Fails if: retention, not activation, is where users actually drop off.
Evidence to get this week: the activation-to-retention funnel for the last 3 cohorts.
Cheapest test: pull the funnel. One afternoon, no engineering.
Claim: AI onboarding raises activation.
Fails if: AI onboarding adds setup anxiety for first-time users.
Cheapest test: a 5-user moderated walkthrough of a clickable prototype.
It also tells you what is already well-reasoned and what it could not assess. A useful red team does not manufacture doubt to look smart. If the plan is strong, it should say so.
Five real kill-assumptions with tests beat twenty generic risks.
For PMs: run it on your own roadmap before the review, not after. The point is to kill a bad bet on a Tuesday instead of defending it in front of leadership a quarter later.
3. The New Plugin: The AI Shipping Kit
The other half of the job changed this year. PMs and founders are now accountable for code an AI wrote.
AI writes fast, but it leaves no written record of intent:
what the system should do,
who may do what,
where the secrets live,
which permissions are actually enforced,
which rules are verified by tests.
The AI Shipping Kit restores that record.
The umbrella command, /ship-check, answers the question you actually have:
Is this safe to ship?
It:
documents the system,
audits the code against that documented intent,
maps test coverage,
and compiles a shipping packet a human can sign off on.
The gate is intended vs. implemented.
/ship-check looks for the places where the product promise and the repo disagree: the permission that is documented but never enforced, the scheduled-job endpoint anyone can call, the test that proves nothing about the workflow it claims to cover.
You do not need to be technical to run it.
You need to know what the system was supposed to do.
The kit has two skills:
shipping-artifacts defines the docs that make an AI-built app reviewable: architecture, flows, permissions, variables, tests, and conditional docs for email, scheduled jobs, SEO, or automation.
intended-vs-implemented audits the gap between documented intent and actual code, with evidence on both sides.
And five commands:
/document-app creates the system documentation.
/security-audit-static checks security against the documented intent.
/performance-audit-static checks over-fetching, missing indexes, and caching.
/derive-tests maps what is tested, what is proposed, and what is unverified.
/ship-check runs the full sequence and compiles the shipping packet.
For PMs: “the AI wrote it” is not a sign-off. /ship-check turns a agent-engineered repo into something a human can put their name on.
4. How to Install It
The repo is the source of truth: https://github.com/phuryn/pm-skills
If you use Claude Cowork, install the whole marketplace:
Open Customize in the bottom-left corner.
Go to Browse plugins -> Personal -> +.
Select Add marketplace from GitHub.
Enter https://github.com/phuryn/pm-skills
All 9 plugins install at once. Enable those you need:
If you use Claude Code, add the marketplace:
claude plugin marketplace add phuryn/pm-skillsThen install the plugins you want. To install the full marketplace:
claude plugin install pm-product-discovery@pm-skills
claude plugin install pm-product-strategy@pm-skills
claude plugin install pm-execution@pm-skills
claude plugin install pm-market-research@pm-skills
claude plugin install pm-data-analytics@pm-skills
claude plugin install pm-go-to-market@pm-skills
claude plugin install pm-marketing-growth@pm-skills
claude plugin install pm-toolkit@pm-skills
claude plugin install pm-ai-shipping@pm-skillsIf you only want the new and updated pieces from this release:
claude plugin install pm-execution@pm-skills
claude plugin install pm-ai-shipping@pm-skillsNew to Claude Code? Start with the beginner’s guide, then the advanced guide when you want the power-user setup.
The commands flow into each other. A real week looks less like a feature list and more like one continuous thread:
/discover a new idea,
/write-prd the winner,
/red-team-prd the PRD before the review,
/ship-check once the code exists.
After any command finishes, it suggests the natural next one.
One more note: the skills are portable. The slash commands are Claude-specific, but the SKILL.md files follow the universal skill format and can be copied into tools like Codex CLI, Cursor, Gemini CLI, OpenCode, or Kiro.
The README has the exact copy instructions.
5. How It Composes With PM Brain
PM Skills gives Claude the method. PM Brain gives Claude your product context.
PM Brain is a markdown second brain for product managers: strategy, users, decisions, hypotheses, stakeholders, and recurring knowledge in plain files on your laptop.
Run them together and the frameworks stop being generic.
/red-team-prd can attack your plan using what PM Brain knows about your real constraints. /strategy can build on your actual positioning. /ship-check can review a repo against documented product intent instead of a blank canvas.
One supplies the rigor. The other supplies the context.
6. Start Here
If you have a plan you are not sure about, run:
/red-team-prd [your PRD, roadmap, or strategy]If you have an AI-built app you are close to shipping, run:
/ship-check [repo or folder]If you are starting from zero, run:
/discover [your product idea]Everything is free and MIT-licensed. If it helps, star the repo so the next PM finds it.
AI does not fix weak product judgment.
It scales it.
PM Skills is where the judgment lives.
Thanks for Reading The Product Compass
It’s amazing to learn and grow together.
Have a great rest of the week,
Paweł
Resources
Get the marketplace (free):
PM Skills on GitHub - 9 plugins, 68 skills, 42 commands, MIT-licensed.
PM Brain - the markdown second brain that composes with it. MIT.
Go deeper (The Product Compass):
Claude Cowork for PMs - agents without IDE, start here.
Claude Code: the beginner’s guide - start here if you are new to IDE.
Claude Code: the advanced guide - the power-user setup after you get the basics.
Codex setup for PMs - wiring a second model alongside Claude. I've found it catches ~80% of my errors.
Intent engineering for AI agents - lead with context, not instructions.
I don’t review the code, I review the artifacts - the review method behind the AI Shipping Kit, plus the downloadable artifact prompt pack.
Security and performance testing prompts - the worked teardowns the kit automates.
Claude Code's Limits Are Generous. The Problem Is Your Setup - how I cut my Claude costs over 5.5x.
Three CLAUDE.md Blocks That Make Claude Get Smarter Every Session - critical concepts for building self-improving agentic systems.
Vibe Coding vs. Vibe Engineering published in Sep, 2025 (in 2026, labeled “agentic engineering” by Andrej Karpathy)
If you are curious, a few things I’m shipping:
claude-usage - Embed your Claude Code usage dashboard (token counts, costs, sessions, projects) directly inside VS Code.
agentlift - Deploy agents to Claude Managed Agents, AWS Bedrock AgentCore, and Google. One folder, one definition, one command.
Grok Build for VS Code - The only visual UI for Grok Build (non-CLI), 1,400 active installations. A bet in case Grok surprises us.