deanpeters/Product-Manager-Skills

altitude-horizon-framework

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

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

pestel-analysis

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

원문 언어: 영어

pol-probe

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

원문 언어: 영어

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.

원문 언어: 영어

recommendation-canvas

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

원문 언어: 영어

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-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.

원문 언어: 영어

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-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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

competitive-analysis-process

Orchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.

원문 언어: 영어

intel-discipline-advisor

Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill. Use when you know something needs researching but not which channel to run.

원문 언어: 영어

intelligence-collection-disciplines

Run competitive research like an intelligence agency: eight collection disciplines (OSINT to MASINT), signal-to-inference chains, and fusion. Use when one-source research isn't enough.

원문 언어: 영어

lifecycle-play-advisor

Diagnose where a product sits in its lifecycle and which play fits — extend, replace, or retire. Use when a product is fading and you need the call, not just the worry.

원문 언어: 영어

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.

원문 언어: 영어

product-lifecycle-plays

Map a product's lifecycle stage and choose between extension, replacement, and retirement plays. Use when a product is maturing or declining and the next move isn't obvious.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

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.

원문 언어: 영어

lean-ux-canvas

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

원문 언어: 영어