
launch-plan
Launch planning plugin that builds tiered launch plans with owners and go/no-go gates.
- GitHub stars
- 8.1K
What it does
- Covers a tiered launch plan with named owners, go/no-go criteria, and a readiness scorecard
- Designed for product managers coordinating a release across teams before a launch date
Build a tiered launch plan with owners, go/no-go criteria, and a readiness scorecard.
Add marketplace
/plugin marketplace add deanpeters/Product-Manager-SkillsRun it inside Claude Code once, then install the plugin below.
Install
/plugin install launch-plan@pm-skillsRun it inside Claude Code after adding the marketplace.
Files
Discovered from sourceLaunch Plan
Purpose
Build the plan that makes a launch land: a checklist of what each function must have ready, sized by launch tier, with a named owner, a date, and a status on every row; go/no-go criteria agreed before the gate; and a one-page Launch Readiness Scorecard the launch forum uses to decide.
The sentence to keep in your head: a launch is a business event, not a ship date. Engineering finishing the product is one row. A customer experiences a launch as finding out about it, getting a price, buying it, receiving it, using it, and getting help when it breaks. Each of those belongs to a different function, and the customer sees whichever one is not ready.
The PM orchestrates. The PM does not own every row. This is influence work: make the gaps visible early enough that the people who own them can close them.
Input
Works best with: What is launching and the date that drives it (a conference, a contract, a season, a budget year).
Also useful: The positioning statement, the price decision, the channels you sell through (direct, partners, distributors, marketplaces), the last launch's lessons learned, and who will make the go/no-go call.
Anything supplied with the invocation itself (text after the skill name, a pasted context dump, or
an appended ARGUMENTS: line) counts as answers already given. Use it and skip whatever it covers;
don't re-ask.
Arriving empty-handed? That works too. The skill opens by asking what is launching and what
fixes the date, proposes a tier from your answers, and builds from there. Anything you can't supply
becomes a labeled [NEEDS SOURCE] blank instead of an invented one.
Example invocations:
Launch plan for our route optimizer. GA is June 12, Sales and Support are not briefed.Review our launch checklist for the NFA-500 controller. Trade fair is April 21. I think we forgot distributor price files.
Key Concepts
Right-Size the Launch (the Tier Dial)
Not every launch deserves the same effort. A tier is an agreed size class that decides how many rows apply and how deep each goes.
| Tier 1: Full | Tier 2: Standard | Tier 3: Light | |
|---|---|---|---|
| Typical launch | New platform or generation, new market, new business model, large revenue at stake, new regulatory exposure | Significant new variant, major feature or option, adjacent segment on existing channels | Minor variant, small feature, cost-down invisible to customers |
| Functions engaged | All | Most, lighter depth | Price list, release note, internal notice |
| Gates | Formal go/no-go (often two: order intake, first shipment or GA) | One gate | None unless compliance is touched |
| Output feel | Cross-functional playbook | Working checklist with owners | Punch list |
Score the tier on six criteria, each low / medium / high with a one-line reason: revenue and margin at stake, newness to the customer, newness to the company (new channel, model, or production process), regulatory and safety exposure, installed-base impact (replaces, cannibalizes, or must coexist with what customers own), and channel impact (do partners need new skills, stock, or contracts).
Tier 2 is the default. Never default to Tier 1. Recommend a tier, say why in one line, and let the user move it in either direction. If they go lighter, name what drops out so the choice is informed. If the scores split (low revenue, high regulatory exposure) say so: a Tier 2 launch can carry a Tier 1 compliance workload. Watch for tier inflation (everything is Tier 1, so the checklist becomes noise) and tier deflation (a Tier 1 change labeled Tier 3 to dodge the work).
Readiness by Function
Organize the checklist by function, because that is how ownership works in a matrix organization. These are the functions that most often fail:
- Sales and channel. Briefed and trained before customers hear; partners told early enough to plan stock, training, and their own messaging; quoting and configuration tools updated; demo environments or demo units ready.
- Support, Service, and spare parts. Trained before the first customer; runbooks, diagnostic tools, and escalation paths released; capacity planned for the launch wave; for hardware, spare parts defined, priced, and stocked where the field needs them.
- Operations, supply chain, and production. Capacity and lead times confirmed; ramp sized to the realistic forecast, not the hopeful one; first-article or first-release quality passed.
- Pricing and commercial. Price, discounts, and packaging approved; price lists, billing, and quoting entries created; partner price files sent in time for their cycles.
- Legal, compliance, and certification. Terms, privacy, and security reviews done; for hardware, conformity assessment and country approvals planned. A missing certificate stops shipments no matter how ready everything else is.
- Documentation and training. Guides, safety instructions, and customer training in every language and market you sell into.
- Marketing. Messaging from the positioning statement, web page, data sheets, demos, press, event material.
- Internal enablement. Order handling, customer success, finance, and legal know what changes for them. FAQs and escalation contacts exist.
Four Dates, Not One
Software launches often collapse these into one day. Industrial launches cannot. Name all four, and make the gap between each a deliberate choice:
- Announce. Customers and the market hear.
- Order opens. Quotes and orders accepted, delivery promised.
- First delivery. The product reaches a customer (first shipment, or first tenant live).
- Full support. Service, training, and spare parts available everywhere you sell.
Announcing long before you can deliver stalls sales of the current product while customers wait. Opening orders before capacity is confirmed breaks delivery promises. Delivering before support is ready turns the first customers into the worst reference stories.
Go/No-Go Criteria Are Agreed Before the Gate
A gate is a scheduled decision. Its criteria must be written down, with owners and thresholds, before anyone sees the status. Otherwise the team looks at a mixed picture and talks itself ready.
- Must-pass: if one fails, the launch does not proceed (support trained in launch regions; signed declaration of conformity; security review closed).
- Watch: a failure needs a mitigation and an owner but does not stop the launch (translated guide for a secondary market).
The PM prepares the gate. The forum with decision rights makes the call. This skill never makes the go/no-go decision.
The Launch Readiness Scorecard
The checklist has dozens of rows. The forum needs one page: a row per function, a column per readiness criterion, with status, owner, and evidence.
| Function | Readiness criteria | Status | Owner | Evidence |
|---|---|---|---|---|
| Support | Agents trained, runbook live, escalation path tested | Ready / At risk / Not ready | Named person | Training roster, runbook link |
Three rules keep it honest:
- Status needs evidence. Ready means the evidence in the criterion exists. An owner's optimism is "At risk" until it does.
- Define the statuses before the first review. What makes a row Ready, At risk, Not ready.
- Must-pass rows are marked. One must-pass "Not ready" means the scorecard says no-go, however green the rest looks.
RACI for the work, DACI for the decision. Give each function row a RACI (Responsible, Accountable, Consulted, Informed). Give each gate a DACI: the Driver (usually the PM) prepares it, one Approver decides, Contributors supply status and evidence, the Informed hear the outcome. A go/no-go with two approvers is not a decision.
Owners Are People, Not Departments
"Marketing" is not an owner. Every row needs a named person (or role, if names are confidential) who has agreed to the date. A row the owner has not agreed to is a wish. Mark it At risk.
The Premortem: Imagine the Launch Already Failed
A checklist finds the rows a team forgot. It does not find the failure nobody wants to say out loud. Gary Klein's premortem does: imagine the launch has already failed and explain why. Treating failure as a fact that already happened makes people name more and sharper causes than "what could go wrong?", and it gives quiet doubters permission to speak.
Run it once, after the checklist and criteria are drafted, before the gate:
- Set the scene. "It is six months after launch, and it failed. What happened?"
- Write failure stories alone first. Each function owner writes what failure looks like from where they sit. Writing alone keeps the most senior voice from setting the story.
- List the causes. Actions, inactions, assumptions, dependencies, partners.
- Rank by likelihood and impact. Keep the few drivers that matter.
- Convert every driver into the plan. Each becomes a readiness criterion (must-pass or watch) or a risk with an owner, a trigger, and a response. A story that changes nothing was not finished.
The premortem is a team exercise. AI can prompt it and propose typical failure stories as labeled suggestions. It cannot know why your launch would fail.
Pre-Approval Check: Will This Plan Hold?
Before the forum approves, test it as an approver would:
- Owners: separate owners for delivery, adoption, operation, and measurement. No risk owned by "the team."
- Dependencies: the critical path is named, including outside parties and capacity assumptions.
- Risks: each has a cause, trigger, consequence, response, owner, and remaining exposure.
- Adoption: someone owns whether sales, partners, and customers actually change behavior, not just whether they were trained.
- Evidence: milestones produce evidence (a signed record, a training roster), not just dates.
- Rollback: what pauses orders, what happens to units already delivered, and who decides.
Match the depth to the tier and to how reversible the step is.
Facilitation Source of Truth
Use workshop-facilitation as the interaction protocol when
running this conversationally: heads-up, context dump, numbered choices, one question per turn.
Default entry mode: Guided · set in pm-skills.config.yaml (library-wide default or a per-skill override); the user's own choice in the session always wins. On the first turn, offer all three modes, then open in the default without waiting for a pick: Guided asks the first question, Context dump invites the paste, Best guess asks for a one-sentence minimum and drafts with every assumption labeled.
Anti-Patterns (what this is NOT)
- Not the build plan. Engineering's schedule is one input, not the launch plan.
- Not a campaign plan. Marketing owns that. This plan checks that it exists and is on time.
- Not the go/no-go decision. The forum decides. You prepare the gate.
- Not a pricing decision. See
finance-based-pricing-advisor. - Not the success measures. What "worked" means belongs to
launch-metrics.
Application
Use template.md for the scaffold.
Output convention. The artifact comes first: tier assessment, four dates, checklist by
function, go/no-go criteria, scorecard, risks. Commentary is short and trails it. Draft in two
stages: a working draft where every row carries a provenance tag ([FROM YOU], [RESEARCH],
[AI-SUGGESTED, VALIDATE THIS]) and every unsupplied date, owner, quantity, or threshold is
[NEEDS SOURCE], never a plausible guess; then a committed copy with tags removed, followed by
a ranked Riskiest Assumptions list.
If the PM brings a draft, critique first. Check the tier and its evidence; the four dates; each function for missing rows, missing owners, missing dates, and "green" with no evidence; whether go/no-go criteria were written before the gate and are measurable; the pre-approval check; and where the premortem's drivers landed. Name gaps; don't fill them. Offer rewrites last.
Step 1: Confirm Scope
Establish what is launching and what is new about it, which markets and regions, which channels, what fixes the date, and who makes the go/no-go call. Guard against defaulting to one kind of launch. A SaaS checklist (release notes, feature flags, in-app announcement) misses certification, spare parts, and distributors. A hardware checklist misses security review, billing, and tenant-level rollback. Ask whether the offering includes hardware, installation, or physical service, and whether it is software, and include the rows that apply.
Step 2: Gather Evidence
Offer two things: research (applicable regulations for the category and market, event dates, partner price-list cycles, competitor launch timing if public) and your own artifacts (positioning, roadmap, price calendar, lead times, partner agreements, last launch's lessons). Either, both, or neither is fine.
Step 3: Propose the Tier
Score the six criteria with one-line reasons. Recommend a tier, name what a lighter tier would leave uncovered, and say the forum confirms it. Let the user move it.
Step 4: Set the Four Dates
Ask for, or mark [NEEDS SOURCE]: announce, order opens, first delivery, full support. Work
backward from the fixed date and name the lead times on the critical path (certification, supplier
tooling, translation, partner price-list deadlines, spare parts stocking, security review).
Step 5: Build the Checklist by Function
For each function, the rows that apply at this tier, each with a one-line deliverable ("done" in a
sentence), a named owner, a due date relative to the four dates, and a status. Keep rows the user
supplied; add missing ones as [AI-SUGGESTED, VALIDATE THIS]. Never invent owners or dates.
Step 6: Draft the Go/No-Go Criteria and the Scorecard
Four to eight criteria: what is checked, threshold, evidence, owner, must-pass or watch. Name the gates and who decides at each. Then roll the checklist into the scorecard with written status definitions, RACI per row, and a DACI per gate.
Step 7: Name the Risks, Run the Premortem, Run the Pre-Approval Check
List the top risks (critical-path rows, rows without agreed owners, dates held by outside parties), each with one mitigation and one owner. Run the premortem with function owners and convert every driver. Close with the pre-approval check. Name each gap; don't fill it.
Step 8: Hand Off and Hand Back
The plan ends at "ready." Whether the launch worked is a different question: offer
launch-metrics. Close with a short summary (supplied, inferred,
unknown) and a numbered decision ladder, the evidence-favored option first, labeled (Recommended):
confirm the tier and send rows to owners for agreement; hold a kickoff with all function owners to
fill the [NEEDS SOURCE] rows; move the announce date to close a gap; or reduce scope (fewer
regions first) to protect the support date.
Examples
See examples/sample.md (Fieldlight route optimizer, SaaS, Tier 2) and
examples/sample-industrial.md (Northfield NFA-500 controller,
hardware, Tier 1). The second shows the four dates pulling apart, which SaaS launches rarely see.
Common Pitfalls
Pitfall 1: Treating the Ship Date as the Launch
Symptom: The plan is the engineering schedule with a marketing row added at the end. Consequence: Customers can buy what nobody can onboard, service, or supply. The first customers become negative references. Fix: Plan the four dates and check every function against them.
Pitfall 2: One Checklist Size for Every Launch
Symptom: A small variant gets the 120-row platform checklist, or a platform gets ten rows. Consequence: Teams stop taking the checklist seriously, or big launches go under-prepared. Fix: Score the tier, recommend one, let the user move it. Never default to the heaviest.
Pitfall 3: The PM Owns Every Row
Symptom: The owner column says "PM" all the way down, or names departments. Consequence: Nothing happens on time because the people who do the work never agreed to it. Fix: Every row gets a named owner from the function that does the work, who agrees the date.
Pitfall 4: Compliance Discovered Late
Symptom: A certificate, security review, or country approval appears four weeks before launch. Consequence: Delivery stops. No marketing fixes a product that cannot legally ship or pass a customer's security review. Fix: Put it on the critical path from the start. Ask the compliance owner what each market needs and plan backward from their lead times.
Pitfall 5: The Channel Hears Last
Symptom: Partners learn about the launch with customers, at the announcement. Consequence: They can't quote, stock, or train. They keep selling the old thing, or a competitor's. Fix: Brief partners months ahead, under confidentiality if needed. Check their deadlines.
Pitfall 6: Support Forgotten
Symptom: No rows for Support or Service training, runbooks, tools, or spare parts. Consequence: The first problem takes weeks to fix. Promises fail and the cost of fixing rises. Fix: Make "full support" a dated milestone with its own must-pass criteria.
Pitfall 7: Criteria Written After the Fact
Symptom: Criteria appear in the gate deck, shaped around the current status. Consequence: The gate becomes theater and real risks are rationalized away. Fix: Agree must-pass and watch criteria, thresholds, and owners before the status is reviewed.
Pitfall 8: Announcing Too Early
Symptom: The launch is announced long before orders open or delivery starts, with no plan for the current product. Consequence: Customers delay buying the current product. Revenue dips before the new one arrives. Fix: Make the announce-to-delivery gap a deliberate decision and plan how Sales handles current deals in it.
Pitfall 9: Invented Dates and Quantities
Symptom: The AI-drafted plan has confident lead times, stock levels, and owner names nobody supplied.
Consequence: It looks complete and is wrong. The team commits to dates nobody checked.
Fix: Every unagreed date, quantity, threshold, and owner is [NEEDS SOURCE] until a function supplies it.
Pitfall 10: A Premortem That Changes Nothing
Symptom: Vivid failure stories, a better mood, and a plan that is word-for-word the same. Or AI wrote the stories and no function owner read them. Consequence: The doubts are on record and still unmanaged. The launch fails the way someone predicted. Fix: Every ranked driver ends in the plan as a criterion or an owned risk with a trigger and a response. Stories come from the people who will run the launch.
References
Skill Files
template.md: tier assessment, four dates, checklist, criteria, scorecard, premortem, pre-approval checkexamples/sample.md,examples/sample-industrial.md
Related Skills
positioning-statement: upstream; feeds marketing and sales messagingpress-release: upstream; forces the customer promise into words before launchfinance-based-pricing-advisor: upstream; price and packaging feed the price rowsroadmap-planning: upstream; sets which launches are coming and roughly whenlaunch-metrics: downstream; how the launch is judged after it happens, including whether the premortem's drivers showed upstakeholder-mapping: for owners who have not agreed their rowsdecision-rights-matrix: names the forum and the one approver for each gateeol-process: the other end of the lifecycle; a launch that replaces a product usually needs a sunset plan beside itworkshop-facilitation: interaction protocol
External Frameworks
- Stage-gate: Robert G. Cooper, Winning at New Products, the origin of gates with pre-agreed criteria.
- DACI and RACI: standard decision and responsibility frameworks in product and project practice, used here for the gate and for the rows.
- Premortem: Gary Klein, "Performing a Project Premortem," Harvard Business Review (2007). Facilitation steps adapted from the premortem tool in the MITRE Innovation Toolkit (itk.mitre.org).
- Launch tiering: common product marketing practice with no single originator; this version scores six explicit criteria.
Provenance
Distilled from practitioner experience running cross-functional launch readiness for B2B and industrial products.
From the deanpeters/Product-Manager-Skills README
Product Manager Skills
Ready-made PM skills for your AI assistant. A skill is a short instruction file that teaches an AI how to do one PM job the way a pro would, such as writing a PRD or mapping stakeholders, so you stop re-explaining your process every time.
Try it in five minutes
- Download the starter pack and unzip it.
- In Claude, open Settings → Capabilities → Skills and upload one skill ZIP from inside the folder. Using Claude Code, Codex or something else? Jump to Get Started.
- Start a chat and paste this, swapping in your own details:
Which of these skills fits what's on my desk this week? Here's the situation: [one or two sentences].
You should see Claude name the skill it is using and start asking you questions. Arriving empty-handed is fine: the skills ask for what they need.
╔════════════════════════════════════════════════════════════════════╗
║ ║
║ ██████╗ ███╗ ███╗ ███████╗██╗ ██╗██╗██╗ ██╗ ███████╗
║ ██╔══██╗████╗ ████║ ██╔════╝██║ ██╔╝██║██║ ██║ ██╔════╝
║ ██████╔╝██╔████╔██║ ███████╗█████╔╝ ██║██║ ██║ ███████╗
║ ██╔═══╝ ██║╚██╔╝██║ ╚════██║██╔═██╗ ██║██║ ██║ ╚════██║
║ ██║ ██║ ╚═╝ ██║ ███████║██║ ██╗██║███████╗███████╗███████║
║ ╚═╝ ╚═╝ ╚═╝ ╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝╚══════╝
║ ║
║ 95 battle-tested skills + 6 command workflows ║
║ Claude Code • Cursor • Codex • n8n • OpenClaw • and more ... ║
║ ║
║ v0.86 • November 13, 2026 • CC BY-NC-SA 4.0 ║
╚════════════════════════════════════════════════════════════════════╝
95 battle-tested PM frameworks, ready for Claude, Codex, ChatGPT, and any agent that can read structured knowledge.
Why This Exists
Generic AI output is a PM's worst enemy. When you tell your agent "write a PRD" without shared context, you get a generic document that no stakeholder trusts and no engineer can act on.
This library gives both you and your AI agent the same professional foundation: the why behind each framework, the failure modes to avoid, and the judgment to apply them correctly. You stop repeating yourself. Your agent stops guessing. The work gets better.
The goal is dual — functional and pedagogic in equal measure. Skills equip agents to do PM work at a professional level, and they teach the human PM the reasoning behind each framework — so you can explain it, adapt it, and pass it on. Neither is a byproduct of the other.
Get Started
Choose your setup:
| I use... | Get this | Notes |
|---|---|---|
| Claude Desktop or Claude Web | pm-skills-starter-pack.zip | Unzip, then upload the individual skill ZIPs to Claude Skills |
| Claude Code | Plugin marketplace | /plugin marketplace add deanpeters/Product-Manager-Skills, then /plugin install product-manager-skills@pm-skills for everything, or one lifecycle bundle at a time (see Browse by lifecycle) |
| Codex | pm-skills-codex.zip | Installs .agents/skills and AGENTS.md |
| OpenCode | Copy skills/* to ~/.config/opencode/skills/ (or reuse the Codex ZIP) | OpenCode reads our SKILL.md format as-is. See the install guide |
| Not sure | pm-skills-starter-pack.zip | Start here |
All downloads: GitHub Releases
Start here by situation
Don't know where to begin? Find the line that sounds like your week. Each route is a suggested order, not a pipeline — every skill runs on its own, so skip ahead, reorder, or stop after one. The first prompt is real: paste it, swap in your details, and go.
| If this is you... | Try, in this order | Time | Paste this first |
|---|---|---|---|
| "I have an idea and I don't know if it's real." | problem-framing-canvas → discovery-interview-prep → pol-probe-advisor | ~1–1.5 hr | Frame this problem: field sales reps 'don't use the CRM' and leadership wants gamification. |
| "A request or mandate just landed on my desk." | incoming-request-advisor → stakeholder-mapping → prioritization-advisor | ~1 hr | My VP DM'd me: "Any chance the dashboard redesign lands next sprint? Board's asking." Analyze this before I reply. |
| "I need to understand the market, fast." | market-landscape-scan → competitive-research-snapshot → swot-analysis | ~1–2 hr | Run a market landscape scan on [your market], and tell me the decision it should support. |
| "We keep getting compared and losing." | positioning-workshop → roadmap-planning (going bigger: product-strategy-session, a 2–4 week workflow) | ~2–3 hr | Run a positioning workshop for our API monitoring tool — we keep getting compared to Datadog and losing. |
| "Time to write it down." | prd-development → epic-breakdown-advisor → user-story | ~1.5–3 hr | Build a PRD for self-serve workspace provisioning — here are my discovery notes and the OKR it ladders to. |
| "Our product is getting old." | lifecycle-play-advisor → eol-readiness-advisor → eol-process | ~30–50 min to a decision | Help me decide what to do with [product]. Here's what makes me think it's fading: [signals]. |
| "I'm stepping up a level." | director-readiness-advisor or vp-cpo-readiness-advisor — pick by where you're headed | ~10–20 min | I'm 60 days into a Director role and my old peers now report to me — it's awkward and I'm still doing PM work. Coach me. |
| "I'm new here, or not sure." | The Starter pack — six skills across the craft | — | Install it, then ask: Which of these skills fits what's on my desk this week? |
Why these orders (so you can break them on purpose):
- Idea → problem → people → probe. Name the problem before you ask anyone about it, and ask people before you build anything. The probe comes last because it's the most expensive of the three.
- Request → decode → map → decide. Understand what's really being asked before replying, know who else is in the room, then ask where it fits. Prioritizing first is how a loud VP becomes your roadmap.
- Market → competitors → SWOT. Evidence first, framework last. SWOT on top of no research is opinion with a 2×2 around it.
- Positioning → roadmap. Decide who you're for and why you win before choosing what to build. The strategy session is the full-length version when the question is bigger than a quarter.
- PRD → epics → stories. The why first, then slices, then the smallest writeable pieces. Writing stories first is how a backlog loses its reason.
- Aging → play → readiness → process. The first skill may say "nothing yet" — extending or harvesting is a legitimate answer, and starting here does not commit you to a sunset.
Browse by lifecycle
Product work unfolds in an order: set the outcome before you investigate, investigate before you define, define before you build. The library follows that arc in five bundles, with a sixth that runs underneath all of them. It's a cycle, not a pipeline, so you will loop back, and every skill still runs on its own.
| Bundle | The question it answers | Start with | Claude Code install |
|---|---|---|---|
| Determine | What are we trying to achieve, and what is the market doing? | product-strategy-session, market-landscape-scan, business-health-diagnostic | /plugin install pm-determine@pm-skills |
| Discover | What is the real problem? | problem-framing-canvas, discovery-interview-prep | /plugin install pm-discover@pm-skills |
| Define | Is this solution worth building, and how do we position it? | pol-probe-advisor, positioning-statement | /plugin install pm-define@pm-skills |
| Develop | How do we turn the chosen solution into buildable work? | prd-development, user-story, prioritization-advisor | /plugin install pm-develop@pm-skills |
| Deliver | How do we price it, take it to market, and retire it well? | finance-based-pricing-advisor, lifecycle-play-advisor | /plugin install pm-deliver@pm-skills |
| Drive | How do I work with stakeholders and grow my career? | stakeholder-mapping, director-readiness-advisor | /plugin install pm-drive@pm-skills |
Not sure which bundle? Ask the pm-skills-navigator: describe what's on your desk, and in about five minutes it tells you where the work really is and which skill to open first.
Every bundle includes a few shared helper skills (the facilitation rulebook and the navigator among them), so each works installed alone. The full list, grouped by bundle and by the smaller "motions" inside each, is in catalog/skills-by-bundle.md.
Why this order? Skipping ahead is how teams build the right thing for the wrong problem. Naming the outcome first gives discovery a target, and discovery gives definition something real to test.
On Claude Desktop or Web? Download the bundle pack that matches your phase, or grab single skills from the download shelf.
Lifecycle bundle packs for Claude Desktop / Web
Each pack is a ZIP of upload-ready skill ZIPs. Unzip it, then upload the skills to Claude Skills:
| Pack | Download | What's inside |
|---|---|---|
| Starter | pm-skills-starter-pack.zip | Six core skills across the craft. The best first download |
| Determine | pm-determine-pack.zip | Strategy, finance, market intelligence, customer context (24 skills) |
| Discover | pm-discover-pack.zip | Interviews, surveys, usage data, synthesis, assumptions, problem framing, opportunity trees, journey maps (12 skills) |
| Define | pm-define-pack.zip | Hypotheses, probes, experiments, positioning (9 skills) |
| Develop | pm-develop-pack.zip | PRDs, stories, prioritization, roadmaps, sprint and release rituals, AI agents (16 skills) |
| Deliver | pm-deliver-pack.zip | Launch plans, messaging, sales enablement, pricing, channels, post-launch metrics, activation and retention, and the end-of-life suite (18 skills) |
| Drive | pm-drive-pack.zip | Stakeholders, decision rights, influence, and career transitions (11 skills) |
| All skills | 99-all-skills-pack.zip | All 95 skills |
The older themed packs (02-discovery through 07-lifecycle-eol) were retired in v0.86. Every skill in them lives in a lifecycle pack above.
Install guides
Try It First — Streamlit (beta)
Not ready to wire skills into your agent setup? Run the local playground first and kick the tires in your browser.
pip install -r app/requirements.txt
streamlit run app/main.py
What you can do:
- Learn — browse setup and integration paths without leaving the app
- Find My Skill — describe your situation in plain English and get recommended skills
- Run Skills — run a skill with your own scenario once you know what you want
Multi-provider support: Anthropic, OpenAI, Ollama. API keys via environment variables only (no in-app key entry).
Docs: app/STREAMLIT_INTERFACE.md · app/.env.example
Feedback welcome via GitHub Issues or LinkedIn.
What You Can Get Done
Navigate by what you're actually trying to accomplish:
Framing and strategy
- problem-framing-canvas — MITRE's Look Inward / Look Outward / Reframe sequence; stops teams from solving the wrong problem
- positioning-statement — Geoffrey Moore's template for defining who you serve, what you solve, and how you're different
- product-strategy-session — full strategy arc: positioning → problem framing → solution exploration → roadmap (2-4 weeks)
Stakeholder alignment
- stakeholder-identification — map every stakeholder before engaging anyone: broad brainstorm → allies/audiences/influencers → R/P/D marking → equity lens → narrow to priority targets
- stakeholder-mapping — run two complementary grids (Power × Interest for engagement strategy; Impact × Power for whose voice to elevate) and compare to find the gaps
- stakeholder-engagement-advisor — per-stakeholder engagement planning: diagnoses their profile and context, then delivers tailored message framing, medium, cadence, and a named next action
Customer discovery and research
- discovery-interview-prep — plans Mom Test-style interviews based on your research goals
- opportunity-solution-tree — generates opportunities and solutions, then recommends the best proof-of-concept to test first
- discovery-process — complete discovery cycle: frame → research → synthesize → validate (3-4 weeks)
Prioritization and roadmapping
- prioritization-advisor — asks 3-5 questions about your context, then recommends RICE, ICE, Kano, or the right alternative
- epic-breakdown-advisor — splits large epics using Richard Lawrence's 9 patterns
- roadmap-planning — gather inputs → define epics → prioritize → sequence → communicate (1-2 weeks)
Writing PM deliverables
- user-story — Mike Cohn format + Gherkin acceptance criteria, with anti-patterns
- prd-development — structured PRD: problem → personas → solution → metrics → stories (2-4 days)
- press-release — Amazon Working Backwards: clarify product vision before writing a line of spec
Validation and experimentation
- pol-probe-advisor — recommends which prototype type to run based on your hypothesis and risk level
- pol-probe — template for documenting lightweight validation experiments before building
Finance and growth
- business-health-diagnostic — diagnoses SaaS health across growth, retention, efficiency, and capital using your real metrics
- organic-growth-advisor — McKinsey Growth Pyramid triage: diagnoses whether your constraint is in new segments, geographies, channels, or products
- feature-investment-advisor — build / don't build recommendation using revenue impact, cost, ROI, and strategic value
Market and competitive intelligence
- intel-discipline-advisor — start here: triages the question on your desk into the right intelligence disciplines, cadence, and executing skill
- competitive-analysis-process — the six-step umbrella: landscape → product comparison → customer needs → business baseline → positioning → strategic direction
- The investigation chain: market-landscape-scan → competitive-research-snapshot → competitive-intel-watch → battle-card-builder — each consumes the prior's schema, so research becomes a cadence instead of a one-off deck
- tam-sam-som-calculator — market sizing three ways: your own numbers, guided interview, or autonomous bottom-up research a skeptical CFO can attack one assumption at a time
Aging products: extend, replace, or retire
- lifecycle-play-advisor — start here when a product stops growing: seven transition questions establish the stage, then it picks the play — extend, replace, or retire — and tells you when the honest answer is "nothing yet"
- product-lifecycle-plays — the framework behind that call: the PLC strategy grid, the seven replacement hazards, and a risk register whose last column asks what is Plan B?
- eol-process — the whole sunset in six phases, decide → align → plan → prepare → announce → close, including the post-EOL review everyone skips
- The EOL chain: eol-readiness-advisor → eol-stakeholder-sequence → eol-checklist → eol-internal-enablement → eol-message — every one runs standalone, sized Light/Standard/Heavy by you
Career and leadership transitions
- director-readiness-advisor — coaches PMs through the PM→Director shift across four situations: preparing, interviewing, newly landed, recalibrating
- vp-cpo-readiness-advisor — coaches Directors through VP/CPO transition, including a CEO interview framework for evaluating roles before you accept
- executive-onboarding-playbook — 30-60-90 day diagnostic playbook for VP/CPO transitions
AI product work
- ai-shaped-readiness-advisor — assesses whether you're automating tasks (AI-first) or redesigning how you work (AI-shaped), then tells you which competency to build first
- context-engineering-advisor — diagnoses context stuffing vs. context engineering and guides memory architecture for AI-powered products
- agent-orchestration-advisor — guides multi-agent workflow design across four dimensions
95 Skills, 3 Types
Skills are organized in three tiers that build on each other:
┌────────────────────────────────────────────────────────┐
│ WORKFLOW SKILLS (25) │
│ Complete end-to-end PM processes (days to weeks) │
│ Example: run a full discovery cycle or write a PRD │
└────────────────────────────────────────────────────────┘
↓ orchestrates
┌────────────────────────────────────────────────────────┐
│ INTERACTIVE SKILLS (34) │
│ Guided discovery — 3-5 questions, then recommendations│
│ Example: "Which prioritization framework fits here?" │
└────────────────────────────────────────────────────────┘
↓ uses
┌────────────────────────────────────────────────────────┐
│ COMPONENT SKILLS (36) │
│ Templates for specific PM deliverables (30-90 min) │
│ Example: write a user story with acceptance criteria │
└────────────────────────────────────────────────────────┘
Interactive skills use an Adaptive Decision Ladder. Instead of dumping a framework at you, an interactive skill asks 3-5 targeted questions about your specific context, then offers numbered recommendations — each with a clear "use this when" rationale. You pick a path. The skill executes it and explains the why as it goes. If you want to just learn the framework without doing the work, you can ask that too — the skill coaches you either way. This is ABC — Always Be Coaching — in practice.
Full catalog: by type or by lifecycle bundle, all 95 skills with descriptions, or browse skills/ directly.
How a Skill File Works
Every SKILL.md follows the same structure:
| Section | What it contains |
|---|---|
| Frontmatter | name, description, type, intent, best_for, scenarios |
| Purpose | What this skill does and when to reach for it |
| Input | What you can bring (with example invocations) — inline input is used, not re-asked, and arriving empty-handed is fine: the skill walks you through it |
| Key Concepts | Frameworks, definitions, anti-patterns — with vocabulary explained |
| Application | Step-by-step instructions an agent (or human) can follow |
| Examples | Real-world cases showing both good and bad versions |
| Common Pitfalls | Named failure modes with consequences and corrections |
| References | Related skills and external frameworks |
The best_for frontmatter field lists 3-5 specific scenarios where the skill is most useful — helpful for quickly scanning whether a skill fits your situation.
Why no $ARGUMENTS templating? Other skill libraries use Claude Code's $ARGUMENTS substitution for input. We deliberately don't: it only expands in Claude Code (it renders as literal syntax in Claude Desktop/Web, Codex, and the Streamlit playground), and it teaches the human reader nothing. Instead, every skill has a plain-language ## Input section that works on every runtime — and makes clear you can show up with full context, partial context, or nothing at all and be guided through the rest. Full rationale in CONTRIBUTING.md.
Guided Context Capture. Every interactive skill gathers context the same way. You can go one question at a time, paste what you know, or say "best guess." A pasted dump gets read back to you as Known / Assumed / Missing / Conflicting before any question is asked. You get a recap before anything is generated. Decisions come as a ranked ladder (Recommended first, real alternatives with tradeoffs), and you make the call. The skill never re-asks what you already said or passes a guess off as a fact. Guided is the default opening; change it library-wide or per skill in pm-skills.config.yaml. How it works and why: docs/guided-context-capture.md.
Works With
Claude Code · Claude Desktop · Claude Web · OpenAI Codex · ChatGPT · Cursor · Windsurf · n8n · LangFlow · CrewAI · Gemini · OpenCode · any agent that reads structured markdown
See docs/Platform Guides for PMs.md for platform-specific setup.
Docs
| Document | Purpose |
|---|---|
| Using PM Skills 101 | Beginner-friendly orientation — setup without technical overload |
| Platform Guides for PMs | Tool-by-tool setup chooser for every supported platform |
| Using PM Skills with Claude | Claude Code + GitHub ZIP upload for Claude Desktop/Web |
| Using PM Skills with Codex | Local workspace + GitHub-connected Codex on ChatGPT |
| Using PM Skills with ChatGPT | GitHub app, Custom GPT Knowledge, and Project-based usage |
| Using PM Skills with Slash Commands 101 | Turn skills into reusable slash commands like /pm-story |
| Add-a-Skill Utility Guide | End-to-end guide for generating and validating new skills |
| Market Intelligence Suite Summary | The 14-skill competitive/market research suite: disciplines, chain, and which skill to run when |
| Lifecycle & EOL Suite Summary | The 8-skill lifecycle/sunset suite: the three plays, the EOL chain, and right-sizing |
| Building PM Skills | How raw PM content gets distilled into agent-ready skills |
| START_HERE.md | 60-second onboarding for local repo users |
What's New
v0.86 — November 13, 2026 · The Everyday Work of Product, Now on the Map
- 12 new skills fill the map: Discover gains Dig (
survey-design-advisor,usage-data-investigation,discovery-habits-advisor) and Decode (research-synthesis,assumption-mapping); Develop gains Drumbeat (backlog-refinement-advisor,sprint-planning,release-readiness); Drive gains Delineate (decision-rights-matrix,pm-role-charter); Deliver gains Deepen (activation-design,retention-diagnostic-advisor) - Pick your slice, not all 95: agents are converging on installable plugins and bundles, so the lifecycle bundles let you install what matches your work
- Easier to start: a five-minute path on the README's first screen, a layered
START_HERE.md, a clearer Desktop install, and a docs style guard - Older packs
02-07retired; every skill in them lives in a lifecycle bundle - Library at 95 skills · full story in the release note
v0.85 — November 13, 2026 · Lifecycle Bundles, a Navigator, and the Go-to-Market Gap Filled
- Six installable lifecycle bundles that follow the product arc: Determine, Discover, Define, Develop, Deliver, plus Drive (stakeholders and career) underneath. Install one with
/plugin install pm-define@pm-skills, or download its pack for Claude Desktop. Every skill still runs on its own pm-skills-navigator: describe what's on your desk and get routed to the right phase and skill- Go-to-market, filled:
launch-plan,launch-metrics,message-house,sales-value-narrative,buying-journey-enablement - Also:
LICENSING.md, an OpenCode install guide, and drift guards for prose counts - Library now at 83 skills · full story in the release note
v0.84 — August 10, 2026 · The Lifecycle & End-of-Life Suite
- 7 new skills + 1 upgrade for the part of product management nobody trains you on: what to do with a product that has stopped growing, and how to retire one without losing the customer
- Start upstream of the kill decision.
lifecycle-play-advisorandproduct-lifecycle-playsdiagnose where a product actually sits using seven transition questions, then pick between the three plays — extend, replace, or retire. Includes the seven replacement hazards and a risk register whose contingency column asks the question everyone skips: what is Plan B? - The EOL chain:
eol-readiness-advisor(go/no-go, and it will tell you to hold) →eol-stakeholder-sequence(Legal before Finance before Sales — get the order wrong and you find the landmines after the announcement) →eol-checklist(phase-gated, an owner on every item) →eol-internal-enablement(your teams ready before customers hear) →eol-message(upgraded: three transition paths including the honest no-replacement case) →eol-process(the whole thing, six phases, including the post-EOL review everybody skips) - Right-sizing is a dial you set, not a verdict handed to you. Every skill offers Light / Standard / Heavy, defaults to Standard, and names what a lighter choice leaves uncovered. A feature deprecation should never get a flagship playbook — that's how teams learn to ignore EOL process on the sunset that actually matters
- No tight coupling. Every skill runs standalone; the workflow is a recommended route through independent stops, not a pipeline. Enter wherever you actually are — including mid-sunset, with a diagnostic that maps symptoms ("Support is drowning") to the phase that got skipped
- Library now at 77 skills · full story in the release note
v0.83 — July 17, 2026 · The Market Intelligence Suite
- 14 new skills + 2 major upgrades — the biggest single addition in the library's history. Run competitive and market research like an intelligence agency instead of a term paper: eight collection disciplines (OSINT → MASINT), signal → inference chains, confidence stacking, and a fusion cadence
- New interaction mode:
autonomous-investigation— the protocol for research that proceeds without you. Question budgets, a search-plan gate, Fact / Inference / Assumption labels on every claim, do-not-invent lists, and stable diffable schemas, so investigations can run on a schedule and you can diff this quarter against last - The investigation chain (market-landscape-scan → competitive-research-snapshot → competitive-intel-watch → battle-card-builder), evidence-cited strategy frameworks (swot-analysis, porters-five-forces, ansoff-matrix), monitors and miners (voice-of-customer-miner, pricing-packaging-tracker, pestel-delta-monitor), and the six-step umbrella competitive-analysis-process
- Upgraded:
tam-sam-som-calculator(three entry modes, including autonomous bottom-up research) andcompany-intel(Executive Signal Refresh rerun pattern — Then/Now diffs and Dropped Language: what leaders stop saying is often the strongest signal) - Library now at 70 skills · full story in the release note
v0.82 — July 8, 2026
- Added
incoming-request-advisor(Interactive) — drop in a Slack ping, email, mandate, or escalation and get a structured breakdown that separates the literal ask from the real job-to-be-done, reads sender power and stake, and points you toward a reply. Ships with a copy/paste template so you can run it by hand too - New: a browsable download shelf at
/dist— no terminal, no Releases tab. Read the plain-language README, scan the CATALOG, and download any skill or pack straight from the repo. Built for PMs who just want the skills - Library now at 56 skills
v0.81 — July 4, 2026
- Every skill now has a required
## Inputsection: what to bring, what happens to context you supply up front (it's used, not re-asked), and reassurance that arriving empty-handed is fine — the guided flow covers the rest - Added
argument-hintautocomplete for Claude Code users; deliberately no$ARGUMENTStemplating — it breaks on every other runtime and teaches the reader nothing (why) - Validator now enforces the convention: skills fail without an Input section or with bare
$ARGUMENTSin the body - Streamlit playground shows each skill's "What to bring (all optional)" before you start a session
- Restored
agent-orchestration-advisor(Interactive) — the multi-agent workflow design skill was referenced everywhere but only existed on an orphaned commit; recovered from git history and brought up to current standards
v0.80 — June 19, 2026
- Added
stakeholder-identification(Component) — comprehensive stakeholder brainstorm using allies/audiences/influencers, R/P/D marking, equity lens, and bias check; narrows to priority targets - Added
stakeholder-mapping(Component) — two complementary grids (Power × Interest + Impact × Power); comparing outputs reveals who you're under-engaging relative to how much the product affects them - Added
stakeholder-engagement-advisor(Interactive) — per-stakeholder engagement planning via Adaptive Decision Ladder: three questions on profile, power/impact, and context deliver tailored message framing, medium, cadence, and a named next action
All three adapted from the MITRE Innovation Toolkit via the companion repo MITRE ITK Skills — worth a bookmark if you work in discovery, facilitation, or cross-functional product strategy.
v0.79 — May 15, 2026
- Added
organic-growth-advisor— McKinsey Growth Pyramid triage for new segments, geographies, channels, or products - Added
pm-skill-creator— interactive skill for designing repo-compliant skills via guided conversation - Fixed missing
.claude-plugin/plugin.jsonthat silently blocked Claude Code skill discovery - Added configurable input length guard (
PM_MAX_INPUT) and path traversal protection to helper scripts
Contributing
Found a gap? Have a PM framework worth formalizing? The bar is pedagogic — skills must teach the why, not just the how.
See CONTRIBUTING.md for guidelines, or open an issue to start a conversation.
License
CC BY-NC-SA 4.0 — non-commercial use with share-alike.
Everything in this repository — every skill, template, and doc — is licensed CC BY-NC-SA 4.0. There is no mix of licenses here.
Some skills note in their Provenance sections that they were adapted from product-manager-prompts, Dean's earlier prompt library. That repo has the same author, so there is no license conflict: a license grants permissions to other people, and a copyright holder is free to adapt and relicense their own work. Those Provenance lines are lineage — a breadcrumb back to where an idea started — not a license dependency. No third-party MIT-licensed text is incorporated anywhere in this library.
In plain terms:
- ✅ Use these skills in your day job — at a for-profit company, with your team, in your agents. That's what they're for.
- ✅ Adapt and remix them — share what you build under this same license, with credit.
- ✅ Teach with them — workshops, brown bags, mentoring, sending the ladder down.
- ❌ Don't sell them — no repackaging the skills themselves into a paid product, course, or service without expressed written permission.
- 📄 Need something citable for your legal team? See LICENSING.md: internal use at a for-profit company is fine, and what you produce using the skills is yours.
- 🤔 Not sure your use qualifies? Open an issue and ask. If you're using these in the spirit they were built — to get better at the craft and help others do the same — the answer is almost certainly yes.
The companion prompt library, product-manager-prompts, carries the same CC BY-NC-SA 4.0 license as of its v2.3.0, with its own plain-language permissions (stricter on commercial use) — see its LICENSING.md, which governs that repo.
Questions
- GitHub Issues: Report bugs or suggest features
- LinkedIn: Dean Peters
- Productside: AI PM consulting and training
Details
- Marketplace
- deanpeters/Product-Manager-Skills
- Source
- skills/launch-plan
- Category
- Strategy
More from deanpeters/Product-Manager-Skills
All 102- lean-ux-canvas
- lifecycle-play-advisor
- market-landscape-scan
- message-house
- opportunity-solution-tree
- organic-growth-advisor
- pestel-analysis
- pestel-delta-monitor
- pm-define
- pm-deliver
- pm-determine
- pm-develop
- pm-discover
- pm-drive
- pm-role-charter
- pm-skill-creator
- pm-skills-navigator
- pol-probe
- pol-probe-advisor
- porters-five-forces
- positioning-statement
- positioning-workshop
- prd-development
- press-release
Similar to launch-plan
More Development Tools
reamorluto/rea466.8K starsReverse engineer anything with agents, from app behavior down to native binaries.
superpowersobra/superpowers319.5K starsCore skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
claude-apianthropics/skills196.9K starsClaude API and SDK documentation skill for building LLM-powered applications
prompts.chatf/prompts.chat178.2K starsAccess thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
agent-sdk-devanthropics/claude-code156.1K starsDevelopment kit for working with the Claude Agent SDK
ui-ux-pro-maxnextlevelbuilder/ui-ux-pro-max-skill152.6K starsProfessional UI/UX design intelligence for AI coding assistants. Includes searchable databases of styles, colors, typography, charts, and UX guidelines for Reac