New advertisers: 50% off your first month with code FIRSTMONTHSee slots

Sales story builder that structures why change, why now, why us, value by role, objections, and do-not-say.

GitHub stars
8.1K
View on GitHub

What it does

  • Covers the narrative in six parts: why change, why now, why us, value by role, objections, and do-not-say

Add marketplace

/plugin marketplace add deanpeters/Product-Manager-Skills

Run it inside Claude Code once, then install the plugin below.

Install

/plugin install sales-value-narrative@pm-skills

Run it inside Claude Code after adding the marketplace.

Files

Discovered from source

Sales Value Narrative

Purpose

Build the story Sales and partners tell: why change, why now, why us, then the value for each person in the buying group, the proof behind each claim, prepared answers to the objections reps actually hear, and a short do-not-say list. The test of a good narrative is whether your champion can retell it to people you will never meet.

It builds on the message-house (the pillars become the spine of "why us") and feeds buying-journey-enablement (which says when each piece gets used). The one-page competitive card is built by battle-card-builder; this skill tells you what the card needs from the narrative.

Input

Works best with: The offering, who you sell to (the roles in the buying group), and the alternative you most often lose to, which is often "do nothing."

Also useful: The message house, win/loss notes, the objections reps hear (from reps, not from the product team), proof you hold, and pricing and packaging.

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 asks who buys and what usually beats you, then drafts the narrative as labeled hypotheses with every proof point and number left as a [NEEDS SOURCE] blank.

Example invocations:

  • Sales narrative for Route Optimizer. We lose to "our dispatchers manage fine in spreadsheets."
  • Objection handling for the NFA-500: price, switching risk, and "our current supplier is fine."

Key Concepts

Narrative, Not Feature Tour

A feature tour starts at your product and leaves the customer to work out why it matters. A narrative starts at the customer's situation and moves to a better outcome, with your offering as the way there. In a group purchase the person you're talking to has to sell the decision internally. Give them a story they can retell.

Why Change, Why Now, Why Us (in that order)

  1. Why change? What does the status quo cost? The strongest competitor is usually doing nothing: the spreadsheet, the old machine, the current supplier. Show the cost of staying put in the customer's terms (hours, downtime, errors, risk, compliance).
  2. Why now? What makes delay expensive? A trigger: a regulation, a renewal date, an aging system losing support, rising cost, a new site, an audit. Without a why-now, deals slip to next year's budget.
  3. Why us? What can you do that the alternatives can't, that matters to this customer, and that they can verify? Differentiation they can't check is a claim, not a reason.

Most sales material starts with "why us," which skips the two questions the customer has to answer first.

The Buying Group

Most purchases are decided by a group. Each role weighs different value and fears different risk:

RoleTypical peopleCares aboutFears
UserDispatchers, operators, techniciansEasier daily work, reliabilityMore work, being blamed when it fails
BuyerProcurementPrice, terms, supplier risk, comparable offersOverpaying, an unreliable supplier
Technical evaluatorIT, security, engineering, maintenanceIntegration, standards, security, supportabilityIntegration failure, non-compliance
FinanceController, CFOPayback, total cost, budget fitAn investment that doesn't pay back, hidden costs
SponsorVP, plant or operations headThe outcome they ownA failed project with their name on it

Add gatekeepers and influencers (consultants, integrators) when they matter. In channel sales the partner is a role too: they need a reason to sell you instead of another brand. Write value per role. If every role gets the same message, it's generic.

Proof: Sourced or Flagged

A claim without proof is an opinion. Strongest first: independent test or certification; named reference with written permission; measured result from a pilot or installed base; internal test with the method available; a calculation the customer can repeat with their own numbers; an unsupported claim (not proof). Every proof point is sourced or [NEEDS SOURCE]. Never invent proof: no made-up customers, quotes, percentages, or awards. A rep who repeats one invented claim to a technical evaluator loses the deal and the credibility. Comparative claims about a named competitor carry legal risk; have Legal review them before they leave the building.

Objection Handling

Objections are information. The structure: Acknowledge without arguing; Clarify what's behind it ("too expensive" can mean over budget this year, more than a competitor's quote, or "I don't believe the savings"); Respond with proof matched to the real concern; Confirm it answered. Prepare answers for the objections Sales actually hears, collected from reps, partners, and win/loss reviews, not the ones the product team would like to answer. Common ones: price, switching risk, compatibility with what they have, "our current approach is fine," support coverage, security, and "we'll wait for next budget."

Trap Questions and the Do-Not-Say List

A trap question leads the customer to discover a weakness in the alternative. It's safe only when you hold the documented answer. Never ask what you can't evidence: a trap built on a guess hands the competitor the stage. A do-not-say list protects reps from claims that are outdated, unprovable, or invite a counter. Teams skip it most, and it saves the most deals.

The Narrative and the Battle Card

The narrative stays the same across competitors. What changes per alternative that keeps winning (each named competitor, plus the status quo) is the traps, the proof, and the do-not-say list, and that is the battle card: one page, thirty seconds, with an as-of date, because competitive facts go stale. Use battle-card-builder to research and draft each card from public evidence. This skill supplies the story and the objections it rests on.

Enablement Is Collaboration

The PM brings the value logic, proof, and competitive facts. Sales brings what customers really say and what works in the room. Partners bring what their people can carry beside a dozen other brands. Build it with them, test it with two or three reps on real accounts, and revise. A narrative the PM writes alone and hands over at a launch event is rarely used.

Facilitation Source of Truth

Use workshop-facilitation as the interaction protocol when running this conversationally.

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 a pitch deck. It is the story and logic a deck should follow.
  • Not messaging architecture. That is the message-house.
  • Not a battle card. See battle-card-builder.
  • Not invented proof. Every claim is sourced or flagged.

Application

Use template.md for the scaffold.

Output convention. Artifact first: scope, why change / why now / why us, value by role, proof, objections, traps, do-not-say, what each competitor card needs. Commentary short, after. Two stages: a working draft where every line carries a provenance tag ([FROM YOU], [RESEARCH], [AI-SUGGESTED, VALIDATE THIS]) and unsupported proof is [NEEDS SOURCE]; then a committed copy with tags removed, followed by a ranked Proof to Gather list and the Questions to Ask Reps list.

If the PM brings a deck or narrative, critique first. Does it open with why us? Is the status quo named as a competitor? Is there a why-now? Is value written per role? Is every claim sourced, and every comparison cleared by Legal? Are the objections ones reps actually hear? Is there a do-not-say list? Name gaps; offer rewrites last.

Step 1: Confirm Scope

The offering, the roles in the buying group, the sales motion (direct, partner, self-serve with sales assist), and the alternatives that win, including the status quo.

Step 2: Cost of the Status Quo

In the customer's terms, with a source or [NEEDS SOURCE]. Offer a calculation they can repeat with their own numbers.

Step 3: Why Now

Name the trigger events that make delay expensive for this segment, and how a rep spots them.

Step 4: Why Us, From the Message House

Take the pillars and proof. If no house exists, draft the differentiators and note that other material may drift from them.

Step 5: Value by Role

One short block per role: what they care about, the value in their terms, the proof they trust, the risk to defuse.

Step 6: Objections, Traps, and Do-Not-Say

Collect real objections from reps. Write acknowledge-clarify-respond-confirm answers. Add trap questions only where you hold the evidence. Write the do-not-say list.

Step 7: Hand Off and Hand Back

Note which competitors and status-quo patterns each need a card (point to battle-card-builder), and where each piece is used (point to buying-journey-enablement). Close with a short summary and a numbered ladder, evidence-favored first, labeled (Recommended): test it with two reps on live deals; gather the missing proof; build a card for the status quo first; or write the partner version.


Examples

See examples/sample.md (Fieldlight Route Optimizer, SaaS) and examples/sample-industrial.md (Northfield NFA-500, hardware).


Common Pitfalls

Pitfall 1: Starting With Why Us

Symptom: The deck opens with company history and features. Consequence: The customer never agrees there is a problem worth solving. Fix: Open with the cost of the status quo, then why now, then why us.

Pitfall 2: Ignoring "Do Nothing"

Symptom: The narrative compares only against named competitors. Consequence: You lose to the spreadsheet or the old machine. Fix: Name the status quo as a competitor and price it.

Pitfall 3: One Message for Every Role

Symptom: The same value statement goes to the user, the buyer, and finance. Consequence: It speaks to none of them. Fix: Write value per role with the proof that role trusts.

Pitfall 4: Objections From the Product Team

Symptom: The objection list is what the product team wishes customers asked. Consequence: Reps meet the real objection with no answer. Fix: Collect from reps, partners, and win/loss.

Pitfall 5: Traps Built on Guesses

Symptom: A rep asks a trap question about a competitor weakness nobody verified. Consequence: The customer or the competitor corrects them, in public. Fix: Ask only what you can evidence.

Pitfall 6: No Do-Not-Say List

Symptom: Reps repeat last year's claims. Consequence: Outdated or unprovable claims reach technical buyers. Fix: Keep a short, dated do-not-say list.

Pitfall 7: Invented Proof

Symptom: AI-drafted narrative with confident percentages and customer names. Consequence: One false claim loses the deal and the credibility. Fix: Sourced or [NEEDS SOURCE]. Never invent.

Pitfall 8: Written Alone, Handed Over at Launch

Symptom: The PM writes it and presents it once. Consequence: Nobody uses it. Fix: Build it with reps and partners and test it on live accounts.


References

Skill Files

Related Skills

External Frameworks

  • Buying group and buying jobs: common B2B sales research on committee purchasing.
  • Objection handling (acknowledge, clarify, respond, confirm): standard sales practice with no single originator.

Provenance

Distilled from practitioner experience enabling sales and partner teams on B2B and industrial offerings.

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

  1. Download the starter pack and unzip it.
  2. 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.
  3. 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.


GitHub stars GitHub forks GitHub watchers Contributors PRs Welcome

Version Skills Last commit Claude Code Plugin

╔════════════════════════════════════════════════════════════════════╗
║                                                                    ║
║   ██████╗ ███╗   ███╗    ███████╗██╗  ██╗██╗██╗     ██╗     ███████╗
║   ██╔══██╗████╗ ████║    ██╔════╝██║ ██╔╝██║██║     ██║     ██╔════╝
║   ██████╔╝██╔████╔██║    ███████╗█████╔╝ ██║██║     ██║     ███████╗
║   ██╔═══╝ ██║╚██╔╝██║    ╚════██║██╔═██╗ ██║██║     ██║     ╚════██║
║   ██║     ██║ ╚═╝ ██║    ███████║██║  ██╗██║███████╗███████╗███████║
║   ╚═╝     ╚═╝     ╚═╝    ╚══════╝╚═╝  ╚═╝╚═╝╚══════╝╚══════╝╚══════╝
║                                                                    ║
║   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 thisNotes
Claude Desktop or Claude Webpm-skills-starter-pack.zipUnzip, then upload the individual skill ZIPs to Claude Skills
Claude CodePlugin 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)
Codexpm-skills-codex.zipInstalls .agents/skills and AGENTS.md
OpenCodeCopy skills/* to ~/.config/opencode/skills/ (or reuse the Codex ZIP)OpenCode reads our SKILL.md format as-is. See the install guide
Not surepm-skills-starter-pack.zipStart 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 orderTimePaste 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 hrFrame 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 hrMy 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 hrRun 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 hrRun 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 hrBuild 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 decisionHelp 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 minI'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.

BundleThe question it answersStart withClaude Code install
DetermineWhat 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
DiscoverWhat is the real problem?problem-framing-canvas, discovery-interview-prep/plugin install pm-discover@pm-skills
DefineIs this solution worth building, and how do we position it?pol-probe-advisor, positioning-statement/plugin install pm-define@pm-skills
DevelopHow do we turn the chosen solution into buildable work?prd-development, user-story, prioritization-advisor/plugin install pm-develop@pm-skills
DeliverHow 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
DriveHow 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:

PackDownloadWhat's inside
Starterpm-skills-starter-pack.zipSix core skills across the craft. The best first download
Determinepm-determine-pack.zipStrategy, finance, market intelligence, customer context (24 skills)
Discoverpm-discover-pack.zipInterviews, surveys, usage data, synthesis, assumptions, problem framing, opportunity trees, journey maps (12 skills)
Definepm-define-pack.zipHypotheses, probes, experiments, positioning (9 skills)
Developpm-develop-pack.zipPRDs, stories, prioritization, roadmaps, sprint and release rituals, AI agents (16 skills)
Deliverpm-deliver-pack.zipLaunch plans, messaging, sales enablement, pricing, channels, post-launch metrics, activation and retention, and the end-of-life suite (18 skills)
Drivepm-drive-pack.zipStakeholders, decision rights, influence, and career transitions (11 skills)
All skills99-all-skills-pack.zipAll 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

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

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

AI product work


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:

SectionWhat it contains
Frontmattername, description, type, intent, best_for, scenarios
PurposeWhat this skill does and when to reach for it
InputWhat 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 ConceptsFrameworks, definitions, anti-patterns — with vocabulary explained
ApplicationStep-by-step instructions an agent (or human) can follow
ExamplesReal-world cases showing both good and bad versions
Common PitfallsNamed failure modes with consequences and corrections
ReferencesRelated 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

DocumentPurpose
Using PM Skills 101Beginner-friendly orientation — setup without technical overload
Platform Guides for PMsTool-by-tool setup chooser for every supported platform
Using PM Skills with ClaudeClaude Code + GitHub ZIP upload for Claude Desktop/Web
Using PM Skills with CodexLocal workspace + GitHub-connected Codex on ChatGPT
Using PM Skills with ChatGPTGitHub app, Custom GPT Knowledge, and Project-based usage
Using PM Skills with Slash Commands 101Turn skills into reusable slash commands like /pm-story
Add-a-Skill Utility GuideEnd-to-end guide for generating and validating new skills
Market Intelligence Suite SummaryThe 14-skill competitive/market research suite: disciplines, chain, and which skill to run when
Lifecycle & EOL Suite SummaryThe 8-skill lifecycle/sunset suite: the three plays, the EOL chain, and right-sizing
Building PM SkillsHow raw PM content gets distilled into agent-ready skills
START_HERE.md60-second onboarding for local repo users

What's New

v0.86 — November 13, 2026 · The Everyday Work of Product, Now on the Map

v0.85 — November 13, 2026 · Lifecycle Bundles, a Navigator, and the Go-to-Market Gap Filled

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-advisor and product-lifecycle-plays diagnose 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

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 ## Input section: 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-hint autocomplete for Claude Code users; deliberately no $ARGUMENTS templating — 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 $ARGUMENTS in 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.json that silently blocked Claude Code skill discovery
  • Added configurable input length guard (PM_MAX_INPUT) and path traversal protection to helper scripts

→ Full changelog


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

Details

Marketplace
deanpeters/Product-Manager-Skills
Source
skills/sales-value-narrative
Category
Strategy

More from deanpeters/Product-Manager-Skills

All 102

Similar to sales-value-narrative

More Sales & Marketing