37 production-ready skills for product managers, installable as Claude Code skills.
A small library of the product-management workflows I actually reach for — PRD drafting, interview synthesis, pre-mortems, opportunity-cost framing, launch checklists — packaged as Claude Code skills you can drop into your own agent stack.
Powered by frameworks from Shreyas Doshi, Lenny Rachitsky, Teresa Torres, Aakash Gupta, Gibson Biddle, and Nate B Jones. Browse by category, click into any skill for the full writeup and install snippet.
Write clear, developer-friendly API documentation with authentication, endpoints, request/response examples, error handling, and rate limits. Trigger this skill when the user mentions API docs, API documentation, endpoint documentation, developer docs, API reference, or says things like "document this API," "write docs for these endpoints," or "create a developer guide."
Create a concise one-page feature brief for stakeholder alignment before committing to a full PRD. Uses Shreyas Doshi's Three Levels of Product Work to ensure the brief addresses impact, execution, and optics. Trigger this skill when the user mentions feature brief, one-pager, feature proposal, feature pitch, concept doc, or says things like "quick write-up for leadership," "summarize this feature idea," or "I need to pitch this before we spec it."
Transform a problem statement, feature idea, or rough brief into a structured, engineering-ready Product Requirements Document (PRD). Uses Teresa Torres's Opportunity Solution Tree for framing the problem space, Marty Cagan's empowered-team philosophy for solution design, and Shreyas Doshi's Pre-Mortem technique to stress-test before handoff. Trigger this skill whenever the user mentions PRD, product requirements, spec, feature spec, requirements document, or says things like "write up what we're building", "spec this out", or "turn this into a doc engineering can use."
Write customer-facing release notes that highlight value over features. Translates engineering changelogs into benefits users care about. Trigger this skill when the user mentions release notes, changelog, what's new, product update, feature announcement, ship notes, or says things like "write the release notes for this sprint" or "announce what we just shipped."
Write technical specifications with architecture decisions, data models, API designs, and implementation plans. Bridges the gap between PRD and code. Trigger this skill when the user mentions tech spec, technical specification, architecture doc, system design, engineering spec, implementation plan, or says things like "how should we build this," "write the technical approach," or "spec the backend for this."
Write clear, engineering-ready user stories with acceptance criteria following the INVEST principles. Uses Clayton Christensen's Jobs-to-be-Done as the framing layer and breaks each job into testable stories. Trigger this skill when the user mentions user stories, acceptance criteria, story writing, backlog items, sprint stories, or says things like "break this into stories," "write tickets for this," or "what should engineering build first."
Analyze and categorize customer feedback into actionable themes using affinity mapping. Works with support tickets, NPS responses, app reviews, survey results, or interview notes. Trigger this skill when the user mentions customer feedback, support tickets, NPS analysis, app reviews, survey responses, feedback analysis, voice of customer, VOC, or says things like "what are customers saying," "categorize this feedback," or "find patterns in these support tickets."
Transform interview transcripts into structured insights with quotes, patterns, and recommendations. Based on Teresa Torres's Continuous Discovery framework. Handles single interviews or batch analysis of 5-10 interviews in parallel. Trigger this skill when the user mentions interview synthesis, research synthesis, interview analysis, transcript analysis, user interviews, customer interviews, or says things like "summarize these interviews," "what did we learn from research," or "pull insights from these transcripts."
Extract Jobs-to-be-Done statements from research data to uncover innovation opportunities. Uses Clayton Christensen's JTBD framework to move beyond feature requests to underlying motivations. Trigger this skill when the user mentions jobs to be done, JTBD, customer jobs, outcome-driven innovation, job stories, or says things like "what job is the user hiring our product for," "find the underlying need," or "go beyond feature requests."
Create data-backed user personas that go beyond demographics to capture behaviors, motivations, and jobs-to-be-done. Trigger this skill when the user mentions personas, user profiles, user segments, user archetypes, customer profiles, or says things like "who are our users," "create personas for this product," or "define our target users."
Map multiple competitors into a unified landscape with positioning matrices, feature comparisons, and market segment analysis. Broader than single-competitor analysis — this covers the entire competitive field. Trigger this skill when the user mentions competitive landscape, market map, competitive overview, market analysis, industry landscape, or says things like "map out all our competitors," "who's in this space," or "create a market overview."
Create comprehensive competitor analysis using Gibson Biddle's DHM framework (Delight, Hard-to-copy, Margin-enhancing) with strategic positioning insights. Trigger this skill when the user mentions competitor analysis, competitive analysis, competitive intelligence, battlecard, DHM framework, or says things like "analyze this competitor," "how do we compare to [company]," or "build a competitive brief."
Build a complete Go-to-Market strategy with target segments, channels, messaging, pricing approach, launch timeline, and success metrics. Incorporates Aakash Gupta's PLG layers where relevant. Trigger this skill when the user mentions go to market, GTM, launch strategy, market entry, product launch plan, or says things like "how do we bring this to market," "plan the launch," or "GTM for this feature."
Simulate how different stakeholders will react to a proposal and prepare responses. Anticipate objections from engineering, design, leadership, sales, legal, and finance before the meeting happens. Trigger this skill when the user mentions stakeholder management, stakeholder simulation, objection handling, meeting prep for proposal, anticipate pushback, or says things like "how will [person/team] react to this," "prepare me for pushback," or "what questions will the exec team ask."
Score and rank features using RICE, ICE, or weighted scoring frameworks with clear documentation of trade-offs. Trigger this skill when the user mentions prioritization, RICE scoring, ICE scoring, feature ranking, backlog prioritization, stack ranking, weighted scoring, or says things like "help me prioritize these features," "which should we build first," or "rank this backlog."
Categorize tasks as Leverage, Neutral, or Overhead using Shreyas Doshi's LNO framework to maximize impact by focusing energy on what matters most. Trigger this skill when the user mentions LNO, leverage neutral overhead, task categorization, energy management, high leverage work, or says things like "what should I focus on," "categorize my tasks," "where should I spend my energy," or "I'm overwhelmed with tasks."
Shift from ROI thinking to opportunity cost thinking using Shreyas Doshi's framework (inspired by Patrick Collison at Stripe). Evaluate what you're giving up by saying yes to something. Trigger this skill when the user mentions opportunity cost, trade-off analysis, what are we giving up, resource allocation, or says things like "is this the best use of our time," "should we be doing something else instead," or "help me think about trade-offs."
Run a Shreyas Doshi-style pre-mortem to identify failure modes before they happen. Imagine the project has failed and work backward to prevent it. Trigger this skill when the user mentions pre-mortem, premortem, risk analysis, failure analysis, risk assessment, project risks, or says things like "what could go wrong," "stress test this plan," or "identify risks before we start."
Challenge PRDs and specs to find blind spots, hidden assumptions, and potential failure scenarios. Acts as a critical reviewer who asks the hard questions before engineering starts building. Trigger this skill when the user mentions spec review, PRD review, challenge my spec, red team, devil's advocate, poke holes, or says things like "find the problems with this spec," "what am I missing," or "review this PRD critically."
Design A/B tests with proper methodology, sample sizes, and success criteria. More focused than the general experiment-designer — specifically for feature A/B tests that product teams run regularly. Trigger this skill when the user mentions A/B test, split test, feature test, variant test, or says things like "set up an A/B test for this," "should we A/B test this," or "design a split test."
Interpret experiment results with statistical rigor and translate them into clear ship/no-ship recommendations. Handles nuanced scenarios like inconclusive results, guardrail violations, and segment-specific effects. Trigger this skill when the user mentions experiment results, A/B test results, test analysis, statistical significance, interpret results, or says things like "analyze these test results," "should we ship based on this data," or "what do these numbers mean."
Design statistically sound experiments with clear hypotheses, success criteria, and sample size calculations. Goes beyond A/B testing to cover multivariate experiments, quasi-experiments, and feature flag rollouts. Trigger this skill when the user mentions experiment design, hypothesis testing, sample size, statistical significance, test plan, or says things like "design an experiment for this," "how do we test this hypothesis," or "is our sample size big enough."
Build comprehensive metrics frameworks using AARRR pirate metrics or Aakash Gupta's input/output methodology. Define what to measure, how to measure it, and what targets to set. Trigger this skill when the user mentions metrics framework, AARRR, pirate metrics, KPIs, product metrics, metrics strategy, analytics framework, or says things like "set up our metrics," "what should we measure," or "build a metrics dashboard."
Identify and validate your product's North Star metric with supporting input metrics. The North Star is the single metric that best captures the value you deliver to customers. Trigger this skill when the user mentions north star metric, NSM, one metric that matters, single key metric, or says things like "what's our north star," "what one number should we track," or "define our key metric."
Diagnose conversion funnel problems and generate data-backed improvement hypotheses. Works with any multi-step flow: signup, onboarding, checkout, upgrade, feature adoption. Trigger this skill when the user mentions funnel analysis, conversion diagnosis, drop-off analysis, funnel optimization, or says things like "where are we losing users," "diagnose this funnel," or "why is conversion low."
Generate competing hypotheses for product problems, evaluate evidence for each, and recommend next steps. Prevents confirmation bias by forcing multiple explanations. Trigger this skill when the user mentions hypothesis generation, root cause analysis, competing hypotheses, diagnostic framework, or says things like "why is this happening," "generate hypotheses for this problem," or "what could explain this."
Debug metrics drops with first principles. When a key metric suddenly changes, systematically identify whether it's a real product issue, a data issue, or an external factor. Trigger this skill when the user mentions metrics drop, metric debugging, KPI drop, dashboard anomaly, or says things like "our metric just dropped," "why did [metric] go down," "something looks off in the data," or "investigate this metrics change."
Design dashboards that show the right metrics to the right audience with clear hierarchy and actionable layout. Trigger this skill when the user mentions dashboard design, analytics dashboard, metrics dashboard, reporting dashboard, or says things like "design a dashboard for [audience]," "what should we show on the dashboard," or "organize our metrics display."
Design onboarding flows that guide users to value quickly. Focuses on time-to-value optimization and activation rate improvement. Trigger this skill when the user mentions onboarding, first-time experience, FTUE, activation flow, welcome flow, setup wizard, time to value, or says things like "design the onboarding," "users are dropping off during setup," or "improve our first-time experience."
Generate your daily plan aligned to goals and priorities using Shreyas Doshi's LNO framework. Start every day knowing what to focus on and what to defer. Trigger this skill when the user mentions daily plan, today's priorities, daily focus, morning planning, day planning, or says things like "plan my day," "what should I focus on today," or "help me prioritize today."
Create comprehensive launch checklists customized to release type (new feature, major release, beta, hotfix). Ensures nothing falls through the cracks across engineering, design, marketing, support, legal, and analytics. Trigger this skill when the user mentions launch checklist, release checklist, go-live checklist, launch readiness, ship checklist, or says things like "are we ready to launch," "create a launch plan," or "what do we need before we ship."
Generate structured meeting agendas with time blocks, objectives, and expected outcomes. Uses the SCQA framework for framing discussion topics. Trigger this skill when the user mentions meeting agenda, agenda, meeting prep, meeting structure, or says things like "create an agenda for this meeting," "structure this discussion," or "prep me for this meeting."
Write executive stakeholder updates using the SCQA (Situation-Complication-Question-Answer) framework. Tailored to audience: executives get outcomes, engineering gets details. Trigger this skill when the user mentions stakeholder update, status update, executive update, weekly update, monthly report, progress report, or says things like "write my weekly update," "send a status to leadership," or "update stakeholders on progress."
Generate weekly priorities aligned to quarterly goals. Know what matters this week and what can wait. Trigger this skill when the user mentions weekly plan, weekly priorities, week planning, sprint planning personal, or says things like "plan my week," "what should I focus on this week," or "set weekly priorities."
Identify AI/ML opportunities for your product. Evaluates where AI can create genuine user value vs. where it's just hype. Inspired by Nate B Jones's pragmatic approach to AI-first product strategy. Trigger this skill when the user mentions AI strategy, AI opportunities, AI features, ML opportunities, where to use AI, AI product strategy, or says things like "where should we use AI in our product," "find AI opportunities," or "should we add AI to this feature."
Review PRDs and feature specs from the user's perspective to predict adoption, support burden, and satisfaction impact. Simulates how real users will experience the product before it's built. Trigger this skill when the user mentions product review, user perspective review, adoption prediction, UX review, customer impact review, or says things like "review this from the user's perspective," "will users actually use this," or "predict how customers will react."
Plan fast iteration cycles using AI-first workflows. Inspired by Nate B Jones (volume over perfection) and Lenny Rachitsky (AI-first PM workflows using PRDs and Markdown to keep AI agents aligned). Trigger this skill when the user mentions rapid iteration, fast shipping, iteration planning, build-measure-learn, speed of execution, or says things like "how do we ship faster," "plan our iteration cycles," "help us move quicker," or "set up a rapid prototyping process."