- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add deanpeters/Product-Manager-Skills --skill pm-skills-navigator -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add deanpeters/Product-Manager-Skills --skill pm-skills-navigator -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add deanpeters/Product-Manager-Skills --skill pm-skills-navigator -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add deanpeters/Product-Manager-Skills --skill pm-skills-navigator -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/deanpeters/Product-Manager-Skills/tree/HEAD/plugins/pm-define/skills/pm-skills-navigator來自發布者
Get from "here's what's on my desk" to "here's the skill to open first, and why", in about five minutes. The library has dozens of skills. Most PMs don't need a catalog; they need a place to start and a sense of what comes next.
The navigator works by finding where the work is in the product lifecycle, because the most common mistake in product work is doing a later job before an earlier one is finished: writing the PRD for a problem nobody has validated, or prioritizing solutions before the outcome is named. The phase tells you which skills are premature.
It recommends a route, not a mandate. Every skill it points to runs on its own.
Works best with: The situation on your desk, in a sentence or two: what's happening, and what you're supposed to produce or decide.
Also useful: What you already know for sure versus what you're assuming, who's asking, and how much time you have.
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 first question asks what's on your desk, and the rest are answerable from what you already know. "I don't know" is a valid answer and becomes a labeled assumption in the route.
Example invocations:
Our dispatchers don't use the route optimizer and my VP wants a redesign. Where do I start?I just joined a product team and don't know which of these skills matters for me.Product work tends to unfold in an order. The library groups its skills by that order:
The same arc shows up in software delivery (plan, analyze, design, build, deploy) and in other product frameworks. That's the point: it isn't a house opinion, it's how work earns the right to move forward.
A team that says "we're in Develop" because a PRD is due, with an unvalidated problem underneath, is actually in Discover. Ask what's validated and what's assumed, and place the work at the earliest phase whose exit condition isn't met. Calling it later doesn't make it later.
Work loops back (a failed test sends you to Discover again) and runs concurrently (launch prep starts while you build). So the navigator:
Each bundle has motions, which are specific jobs. The map below is the full list. A motion marked Coming has no skill yet. The navigator says so instead of forcing a poor fit.
catalog/skills-by-bundle.md.Use workshop-facilitation as the interaction protocol. Give
the heads-up at the start (four questions, about five to ten minutes) and let the user dump context
to skip ahead.
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.
This block is generated from pm-skills.config.yaml. Don't edit it here; run
python3 scripts/check-bundles.py --write-navigator.
Determine (Context): Set outcomes and read the terrain: strategy, finance, market, customers.
product-strategy-session, organic-growth-advisor, business-health-diagnostic, feature-investment-advisor, finance-metrics-quickref, saas-economics-efficiency-metrics, saas-revenue-growth-metricsansoff-matrix, pestel-analysis, porters-five-forces, swot-analysis, tam-sam-som-calculatorcompany-intel, company-research, , , , , , , Discover (Discover + Investigate): Find and frame the real problem.
discovery-interview-prep, discovery-process, opportunity-solution-tree, problem-framing-canvas, problem-statement, customer-journey-map, customer-journey-mapping-workshopsurvey-design-advisor, usage-data-investigation, discovery-habits-advisorresearch-synthesis, assumption-mappingDefine (Discover + Define): Shape a solution worth building and test the bet.
derisk-measurement-advisor, lean-ux-canvas, pol-probe-advisor, pol-probe, recommendation-canvas, epic-hypothesispositioning-statement, positioning-workshop, battle-card-builderDevelop (Create): Turn the chosen solution into buildable work.
prd-development, press-release, storyboarduser-story, user-story-splitting, user-story-mapping, user-story-mapping-workshop, epic-breakdown-advisorprioritization-advisor, roadmap-planningagent-orchestration-advisor, ai-shaped-readiness-advisor, context-engineering-advisorbacklog-refinement-advisor, , Deliver (Deliver): Take it to market, measure it, and retire it well.
launch-plan, message-house, sales-value-narrative, buying-journey-enablementfinance-based-pricing-advisor, pricing-packaging-trackeracquisition-channel-advisorlaunch-metricsactivation-design, retention-diagnostic-advisoreol-checklist, eol-internal-enablement, eol-message, eol-process, , , , Drive (Runs under all five phases): Drive your career and your stakeholders.
incoming-request-advisor, stakeholder-engagement-advisor, stakeholder-identification, stakeholder-mappingaltitude-horizon-framework, director-readiness-advisor, executive-onboarding-playbook, product-sense-interview-answer, vp-cpo-readiness-advisordecision-rights-matrix, pm-role-charterCore (shared helpers that ship with every bundle): workshop-facilitation, pm-skills-navigator, autonomous-investigation, pm-skill-creator, skill-authoring-workflow
This skill asks up to 4 adaptive questions, then recommends a route with reasons.
Agent asks:
"What's the situation? Tell me what's happening and what you're expected to produce or decide. One or two sentences is plenty."
Listen for the job-to-be-done behind the request. "Write a PRD" is a deliverable; the situation underneath (a stakeholder asked for a feature, or discovery found a pattern) decides which phase it belongs to. If the answer is about people (a stakeholder, a request, your career), note it: that's Drive, and it can skip Question 2.
Agent asks:
"Let's find where this really stands. Which of these is true today?
Pick any that apply."
Place the work at the earliest phase whose exit condition is unmet:
If their situation sounds later than their answers (a PRD is due but they picked 4), say so gently: the PRD is premature, here's the evidence gap, and here's the smaller job that unblocks it.
Agent asks:
"What would make this session worth it?
Use the answer to pick the motion and the skill type. A decision usually means an interactive advisor. An understanding usually means a workflow or an investigation. A document means a component skill. Alignment means a Drive skill, whatever the phase.
Agent asks:
"Roughly how long can you give this: under an hour, a few hours, or days?"
Use it to size the route, and honor an override either way. Under an hour means one skill, the quick one. A few hours means two or three in order. Days means the workflow version where one exists. Name what a shorter route leaves uncovered.
Deliver this structure:
## Your Route: [Situation in a few words]
**Where the work is:** [Phase] (and [second phase] if it straddles) — because [what's validated vs assumed]
**Bundle / motion:** [Bundle] → [Motion]
### Start here
1. [`skill`](https://github.com/deanpeters/Product-Manager-Skills/blob/main/skills/skill/SKILL.md): [why this one first, one line]
2. [`skill`](https://github.com/deanpeters/Product-Manager-Skills/blob/main/skills/skill/SKILL.md): [what it adds]
3. [`skill`](https://github.com/deanpeters/Product-Manager-Skills/blob/main/skills/skill/SKILL.md): [optional; what it adds]
**What you're skipping, if anything:** [the earlier-phase job you aren't doing, and the risk]
**Gap, if any:** [a need with no skill yet, and the closest alternative]
### Paste this first
> [A real first prompt using their own details]
### Assumptions I made
- [Anything answered "I don't know"]
Then offer numbered next steps:
"Where next?
Pick a number, combine them, or tell me what you'd rather do."
Fieldlight (field service software). The PM's VP wants a redesign of the route optimizer because dispatchers "don't use it."
Q1. "Dispatchers don't use the route optimizer. My VP wants it redesigned. I'm supposed to write the PRD."
Q2. Which is true: outcome, problem, tested solution? → "Honestly, none. The VP has an outcome in mind, but nobody has asked a dispatcher why."
Q3. What do you walk away with? → "A document, the PRD."
Q4. Time? → "A couple of hours."
Route: Phase Discover (and Develop, where the request is pointing). The PRD is premature: the problem is an opinion, not a finding.
problem-framing-canvas: state the problem before the solutiondiscovery-interview-prep: plan five dispatcher conversationsprd-development: once the problem is evidencedWhat you're skipping: nothing yet; you're not skipping, you're sequencing. Paste this first: "Frame this problem: dispatchers 'don't use' the route optimizer, and my VP wants it redesigned."
The coaching beat: the PRD was the right deliverable and the wrong next step. Naming it that way keeps the PM from feeling blocked.
Northfield Automation (industrial retrofit controls). NFA-200 sales have been flat for six quarters. A distributor asks for a variant; engineering says it's a 14-month cycle.
Q1. "NFA-200 is flat. A big distributor wants a variant. Sales is half-promising it."
Q2. → "We have an outcome (hold margin). We don't know if it's the product or the channel."
Q3. → "A decision: variant or not?"
Q4. → "A week, but it's a big call."
Route: Phase Deliver (an aging product) and Define (the variant is an untested bet). Highest unresolved risk first: Deliver, because nobody has established whether the product is declining or badly distributed.
lifecycle-play-advisor: is this extend, replace, retire, or nothing yet?incoming-request-advisor: decode what the distributor is asking before replyingpol-probe-advisor: if "extend" wins, test the variant cheaplyWhat you're skipping: a 14-month build commitment on an untested variant. Paste this first: "Help me decide what to do with NFA-200: sales flat six quarters, a distributor wants a variant."
The coaching beat: two phases named on purpose. Straddling is normal; what matters is which risk to retire first.
Symptom: "A PRD is due, so we're in Develop." Consequence: A polished spec for an unvalidated problem. Looks like progress, builds the wrong thing well. Fix: Place by evidence: the earliest phase whose exit condition is unmet.
Symptom: Running all three recommended skills in order because they were listed. Consequence: Process theater. The route is a suggestion; the first skill may be all you need. Fix: Stop when the question is answered. Every skill runs alone.
Symptom: Recommending a loosely related skill for a need the library doesn't cover yet. Consequence: The PM trusts a template that doesn't fit, and the library loses credibility. Fix: Say "no skill for this yet" and name the closest honest alternative with its limits.
Symptom: Refusing to help with a later-phase skill until an earlier one is done. Consequence: Contradicts a cycle that really is concurrent, and the PM stops asking. Fix: Name what's being skipped and the risk, then help anyway.
Symptom: Sending a stakeholder conflict to Discover. Consequence: Customer research for a problem that's about a person. Fix: Drive runs under every phase. Route people questions there directly.
These stand on their own; none is a prerequisite for this skill, and this skill isn't a prerequisite for them.
workshop-facilitation: the interaction protocollifecycle-play-advisor: the product-lifecycle question (extend, replace, retire), not to be confused with the work lifecycle used hereintel-discipline-advisor: a deeper navigator for the market-intelligence skillsprioritization-advisor: when the question is "which option", not "which skill"Find the right PM skill for the situation on your desk. Use when you don't know where you are in the product lifecycle or which skill in this library to start with.
---name: pm-skills-navigatordescription: Find the right PM skill for the situation on your desk. Use when you don't know where you are in the product…---# plugins/pm-define/skills/pm-skills-navigator/SKILL.md常見問題
從發布者下載 plugins/pm-define/skills/pm-skills-navigator/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/deanpeters/Product-Manager-Skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。
competitive-analysis-processjobs-to-be-done, proto-persona, voice-of-customer-miner