pm-skills-navigator
Find the right PM skill for the situation on your desk
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill pm-skills-navigatorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of pm-skills-navigator
pm-skills-navigator scores 86/100 on our quality scale, 2326th of 4,700 Development & Engineering skills we index (top 50%).
Its SKILL.md is 23 KB long, well organised into 34 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so pm-skills-navigator is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit โ read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk โ read a skill before letting an agent act on it.
pm-skills-navigator compared with similar skills
All 4 of these similar skills score higher than pm-skills-navigator; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pm-skills-navigator (this skill)by deanpeters | 86 | 7.1k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install pm-skills-navigator?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill pm-skills-navigator. The install tabs above show the steps for each supported agent. - Which AI agents does pm-skills-navigator work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is pm-skills-navigator safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is pm-skills-navigator still maintained?
- The repository was last updated about 3 months ago, so pm-skills-navigator is actively maintained.
Skill content
View source on GitHubname: pm-skills-navigator argument-hint: "[the situation on your desk, in a sentence or two]" description: "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." intent: >- Guided triage from a situation to a route. Places the work on the product lifecycle by what is validated versus assumed, names the bundle and motion that fits, recommends one to three skills in order with a reason each, says plainly when the library has no skill for the need yet, and hands over a paste-ready first prompt. type: interactive theme: navigation best_for:
- "Not knowing which of the library's skills fits the problem on your desk this week"
- "Checking whether you are about to do a later-phase job (a PRD, a roadmap) before an earlier one is done"
- "Learning how the library's skills fit together by lifecycle phase" scenarios:
- "Leadership wants a feature and I can't tell if we should be framing, testing, or specifying it"
- "I'm new to this library and want to know where to start for my product" estimated_time: "5-10 min"
PM Skills Navigator
Purpose
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.
Input
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.
Key Concepts
The Arc
Product work tends to unfold in an order. The library groups its skills by that order:
| Phase (bundle) | The question | You're here when... | You can leave when... | |---|---|---|---| | Determine | What outcome are we after, and what is the market doing? | You can't state the outcome in a measurable sentence, or the market has moved | You have a measurable outcome and a view of the market and the customer | | Discover | What is the real problem? | You have an outcome but the problem is a guess or a stakeholder's opinion | You have a problem statement backed by evidence from customers | | Define | Is this solution worth building, and how do we position it? | You have a problem but the solution is untested | You have a tested bet worth building and can say who it's for and why you win | | Develop | How do we turn it into buildable work? | The solution is chosen but isn't ready for a team (no PRD, stories, order) | A team can start, and knows what they're building and in what order | | Deliver | How do we price it, take it to market, measure it, and retire it well? | It's built, or it's aging | It's priced and launched, and you can tell whether it worked, or it has been retired cleanly | | Drive | How do I work with people and grow? | The question is about a stakeholder, an incoming request, or your own career | It's handled. This phase runs under all the others |
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.
The Phase Is Set by Evidence, Not by Where You Wish You Were
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.
A Cycle, Not a Line
Work loops back (a failed test sends you to Discover again) and runs concurrently (launch prep starts while you build). So the navigator:
- Names two phases when the work straddles them, and puts the one carrying the highest unresolved risk first.
- Treats Drive as orthogonal. A question about a stakeholder or your own career gets routed to Drive whatever phase the product is in.
- Never blocks. If you want a later-phase skill, it says what you're skipping and what that risk is, then helps you anyway. Your call.
Motions: The Smaller Groups Inside a Bundle
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.
Anti-Patterns (what this is NOT)
- Not a pipeline. It suggests an order; it doesn't require one. Skip, reorder, or stop after one.
- Not a gate. It never refuses to help with a later-phase skill.
- Not a replacement for the skills. It points; the skills do the work.
- Not a catalog. For a flat list, see
catalog/skills-by-bundle.md.
Facilitation Source of Truth
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.
The Map
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.
- Direct (Business and product outcomes, strategy, and the finance behind them):
product-strategy-session,organic-growth-advisor,business-health-diagnostic,feature-investment-advisor,finance-metrics-quickref,saas-economics-efficiency-metrics,saas-revenue-growth-metrics - Diagnose (Strategic lenses: SWOT, Porter's, Ansoff, PESTEL, TAM/SAM/SOM):
ansoff-matrix,pestel-analysis,porters-five-forces,swot-analysis,tam-sam-som-calculator - Detect (The market and competitor investigation chain):
company-intel,company-research,competitive-analysis-process,competitive-intel-watch,competitive-research-snapshot,intel-discipline-advisor,intelligence-collection-disciplines,market-landscape-scan,pestel-delta-monitor - Describe (Who the customer is: jobs, personas, voice of customer):
jobs-to-be-done,proto-persona,voice-of-customer-miner
Discover (Discover + Investigate): Find and frame the real problem.
- Drill-down (Interviews, problem framing, opportunity solution trees, journey maps):
discovery-interview-prep,discovery-process,opportunity-solution-tree,problem-framing-canvas,problem-statement,customer-journey-map,customer-journey-mapping-workshop - Dig (Collect evidence: surveys, usage data, a steady customer-contact habit):
survey-design-advisor,usage-data-investigation,discovery-habits-advisor - Decode (Make sense of it: synthesis and assumption mapping):
research-synthesis,assumption-mapping
Define (Discover + Define): Shape a solution worth building and test the bet.
- De-risk (Hypotheses, probes, experiments, measurement):
derisk-measurement-advisor,lean-ux-canvas,pol-probe-advisor,pol-probe,recommendation-canvas,epic-hypothesis - Differentiate (Positioning and competitive sales tools):
positioning-statement,positioning-workshop,battle-card-builder
Develop (Create): Turn the chosen solution into buildable work.
- Document (PRDs, press releases, storyboards):
prd-development,press-release,storyboard - Draft (User stories, splitting, story mapping, epic breakdown):
user-story,user-story-splitting,user-story-mapping,user-story-mapping-workshop,epic-breakdown-advisor - Decide (Prioritization and roadmaps):
prioritization-advisor,roadmap-planning - Delegate (Work with AI agents: orchestration, context engineering, readiness):
agent-orchestration-advisor,ai-shaped-readiness-advisor,context-engineering-advisor - Drumbeat (Execution rhythm: backlog refinement, sprint planning, release readiness):
backlog-refinement-advisor,sprint-planning,release-readiness
Deliver (Deliver): Take it to market, measure it, and retire it well.
- Debut (Launch planning and messaging):
launch-plan, [message-house](../message-house/
Truncated for display โ read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code โ from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k๐คฏ LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit โ see the Safety scan above for what the skill file itself contains.
