原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Product-Manager-Skills Skill

代码仓库 ↗

作者:deanpeters★ 8,095 (整个仓库)56 个 skill

★ 星标是整个仓库的,不是每个 Skill 的

选择要安装的 Skill

能做什么

此仓库是合集,包含 56 个 Skill

  • 连接方式 供 AI 读取的指令文件
  • 账号或密钥 尚未确认(README 提到密钥或 .env 文件)
  • 分类 写代码
作者的原始说明
Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/deanpeters-product-manager-skills.svg)](https://mcp.popnx.com/en/skills/deanpeters-product-manager-skills)

可搭配使用

在同一工作中把 AI 连到服务的 MCP

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

作者:morluto广泛使用↓ 38.9万/周★ 47万8天前更新

MCP · 连接服务在你的电脑上运行

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

作者:fallow-rs广泛使用↓ 244.1万/周★ 5385昨天更新

MCP · 连接服务在你的电脑上运行

相似的 Skill

同类工作,排序与 Skill 列表相同

与相似项目对比
本项
Product-Manager-Skills
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者deanpetersmorlutomultica-aiGraphify-Labsharry0703
Skill 数561111
GitHub 星标8,095470,165234,528150,695144,727
最近代码更新2026年11月13日2026年11月20日2026年4月20日2026年11月20日2026年11月19日
许可证–MIT–Apache-2.0MIT

deanpeters 提供的 56 个 Skill(指令集),AI 读取后照做 · 不是 MCP server

选择要安装的 Skill

只安装你真正会用的。点开名称查看该 Skill 的安装方法

这个合集有 56 个 Skill,太多了不适合全部安装:每个 Skill 的说明都会载入每次对话,AI 更容易选错。请从下方列表只选你会用的

  • acquisition-channel-advisor

    Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.

  • agent-orchestration-advisor

    Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.

  • ai-shaped-readiness-advisor

    Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.

  • altitude-horizon-framework

    Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

  • business-health-diagnostic

    Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.

  • company-intel

    Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.

  • company-research

    Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.

  • context-engineering-advisor

    Diagnose context stuffing vs. context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably.

  • customer-journey-map

    Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.

  • customer-journey-mapping-workshop

    Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario.

  • derisk-measurement-advisor

    Identify what to measure, test, or track to de-risk a product or AI idea. Use when stress-testing an idea across internal (DUFV) and external (PESTEL) dimensions.

  • director-readiness-advisor

    Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.

  • discovery-interview-prep

    Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.

  • discovery-process

    Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.

  • eol-message

    Write a right-sized EOL announcement — brief notice through full phased comms — with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan.

  • epic-breakdown-advisor

    Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.

  • epic-hypothesis

    Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

  • executive-onboarding-playbook

    Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.

  • feature-investment-advisor

    Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.

  • finance-based-pricing-advisor

    Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship.

  • finance-metrics-quickref

    Look up SaaS finance metrics, formulas, and benchmarks fast. Use when you need a quick metric definition, formula, or benchmark during analysis.

  • incoming-request-advisor

    Decode an incoming message into a structured breakdown separating the literal ask from the job-to-be-done. Use when a loaded Slack ping, email, mandate, or escalation needs a reply.

  • jobs-to-be-done

    Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.

  • lean-ux-canvas

    Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.

  • opportunity-solution-tree

    Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

  • organic-growth-advisor

    Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next.

  • pestel-analysis

    Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.

  • pm-skill-creator

    Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.

  • pol-probe

    Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.

  • pol-probe-advisor

    Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.

  • positioning-statement

    Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.

  • positioning-workshop

    Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.

  • prd-development

    Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

  • press-release

    Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet.

  • prioritization-advisor

    Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.

  • problem-framing-canvas

    Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.

  • problem-statement

    Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.

  • product-sense-interview-answer

    Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.

  • product-strategy-session

    Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.

  • proto-persona

    Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.

  • recommendation-canvas

    Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning. Use when deciding whether an AI solution deserves investment or recommendation.

  • roadmap-planning

    Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.

  • saas-economics-efficiency-metrics

    Evaluate SaaS unit economics and capital efficiency. Use when deciding whether the business can scale efficiently or needs correction.

  • saas-revenue-growth-metrics

    Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.

  • skill-authoring-workflow

    Turn raw PM content into a compliant, publish-ready skill. Use when creating or updating a repo skill without breaking standards.

  • stakeholder-engagement-advisor

    Plan engagement for a specific stakeholder. Use when preparing an outreach, navigating resistance, or aligning a critical relationship before a key milestone.

  • stakeholder-identification

    Map every stakeholder before engaging anyone. Use when launching an initiative, scoping discovery, or building an engagement plan from scratch.

  • stakeholder-mapping

    Prioritize stakeholders using two complementary grids. Use when setting engagement strategy and surfacing whose voice needs elevating after stakeholder identification.

  • storyboard

    Create a six-frame storyboard that shows a user's journey from problem to solution. Use when you need a fast narrative for alignment, concept reviews, or demos.

  • tam-sam-som-calculator

    Calculate TAM, SAM, and SOM with explicit assumptions, methods, and caveats. Use when sizing a market for a product idea, business case, or executive review.

  • user-story

    Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.

  • user-story-mapping

    Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

  • user-story-mapping-workshop

    Run a user story mapping workshop with adaptive questions and a structured map output. Use when you need backbone activities, tasks, and release slices for a workflow.

  • user-story-splitting

    Break a large story or epic into smaller deliverable stories using proven split patterns. Use when backlog items are too big for estimation, sequencing, or independent release.

  • vp-cpo-readiness-advisor

    Guide the transition to VP or CPO across preparing, interviewing, landing, and recalibrating. Use when executive product scope is changing fast.

  • workshop-facilitation

    Facilitate workshop sessions in a one-step, multi-turn flow. Use when an interactive skill needs consistent pacing, options, and progress tracking.

Skill 和 MCP 有什么不同

MCP = 手

把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。

Skill = 手册

教 AI 怎么做某项工作的文本文件,不连接任何服务。

有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。

适用的应用

Claude CodeClaude (เว็บ/แอป)CodexCursorOpenCode

依据开发者 README 和 repo 中的文件夹

安装

请先选择 Skill

此仓库有 56 个 Skill。请从上方列表选一个,该 Skill 的页面有完整安装方法,包括让 AI 安装和 ZIP 文件

让 AI 帮你安装
上传到 claude.ai

前往 Skill 列表 ↑

作者的命令会安装整套 56 个
/plugin marketplace add deanpeters/Product-Manager-Skills
/plugin install product-manager-skills@pm-skills

摘自开发者 README,会下载并运行开发者的代码

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

来自 GitHub

GitHub 星标
8,095
星标是整个仓库的,不是每个 Skill 的
开发者
deanpeters
许可证
未注明许可证 此 repo 未注明许可证,默认作者保留所有权利;转发或商用前请先询问作者。
最近代码更新
2026年11月13日
repo 中的 SKILL.md 文件(含译本和模板)
56
主题
ai-agents, ai-product-management, claude-skills, pm-frameworks, product-management