PM Leadership Toolkit

Design rigorous A/B tests with hypothesis formulation, sample size calculation, success criteria, guardrail metrics, and rollout planning. Includes Bayesian vs frequentist guidance and compliance-aware staged rollout for ERP features. Use when someone says "A/B test", "experiment", "split test", "hypothesis", "test this feature", "should we experiment", "sample size", "statistical significance".

AI pricing strategy for SaaS products. Covers embed-vs-charge decisions, AI cost modeling, value quantification, packaging AI features, WTP research, and AI-specific pricing metrics. Use when someone says "AI pricing", "how to price AI", "price AI feature", "AI add-on", "AI copilot pricing", "AI agent pricing", "charge for AI", "AI monetization", "AI cost model", "inference costs", "AI credits", "AI packaging", "per-agent pricing", "AI willingness to pay", "AI embed or charge", "AI margin", "copilot tax", or "AI pricing strategy".

Per-competitor sales battlecard — a 1-page scannable cheat sheet a rep pulls up mid-call. Competitive positioning, objection handling, landmine questions, proof points, and deal stage guidance. Use when someone says "battlecard", "competitive cheat sheet", "how do we sell against", "competitor comparison", "competitive positioning", "sales enablement", "win against", "deal strategy against [competitor]", "they're evaluating [competitor]".

Generate content for board or investor deck presentations. Creates the narrative arc, key slides content, and talking points. Covers: market context, product progress, metrics, roadmap, asks. Use when someone says "board deck", "investor deck", "board meeting", "quarterly board update", or "prepare for the board".

Build/buy/partner decision framework with scoring across time-to-value, TCO, strategic control, and integration complexity. Use when someone says "build or buy", "build vs buy", "should we build this", "vendor evaluation", "make or buy", "partnership evaluation", "third-party vs in-house", "buy vs partner".

Customer success playbook generator for lifecycle stages: onboarding, adoption, expansion, renewal, churn prevention. Creates playbooks with triggers, actions, owners, and health indicators. Domain-aware: adapts to compliance and onboarding requirements from domain-context.md. Use when someone says "customer success", "CS playbook", "onboarding playbook", "churn prevention", "renewal", "expansion", "customer health", "lifecycle", "adoption", "NRR".

Analytics dashboard design tool. Defines audience, selects leading + lagging metrics, designs information hierarchy, and specifies data sources. Follows dashboard design principles: most important metric top-left, comparison context, anomaly highlighting. Use when someone says "dashboard", "analytics", "metrics dashboard", "KPI dashboard", "reporting", "data visualization", "executive dashboard", "product dashboard".

Create ADR-style product decision records. Documents context, options considered, trade-offs, the decision made, and consequences. Enforces that alternatives were considered. Use when someone says "decision doc", "ADR", "we decided to", "document this decision", "why did we choose", or "decision record".

Structured challenge of product decisions with pre-mortem and counter-arguments. Use when someone says "challenge this", "devil's advocate", "poke holes", "stress test", "pre-mortem", "what could go wrong", "am I missing something", "sanity check this decision".

Generate SCQA-structured executive or investor updates. Covers weekly status reports, monthly business reviews, and quarterly investor updates. Concise, board-ready, focused on outcomes not activities. Use when someone says "executive update", "status report", "investor update", "board update", "what should I report?", or "monthly business review".

Analyze, categorize, and prioritize feature requests using affinity mapping, frequency-severity scoring, and demand curve analysis. Ingest from pasted lists, CSV, or freeform text. Flags compliance/regulatory implications automatically. Use when someone says "feature requests", "customer requests", "what should we build", "request backlog", "prioritize requests", "demand analysis", "feature voting".

Categorize user feedback using affinity mapping. Ingest from multiple sources, de-duplicate, cluster into themes, score by frequency + severity + sentiment, and output a theme map with representative quotes and recommended actions. Distinguishes bugs, feature requests, usability issues, and praise. Use when someone says "categorize feedback", "sort feedback", "feedback analysis", "NPS comments", "what are users saying", "support themes", "voice of customer".

Diagnose conversion funnel drop-offs, generate hypotheses, and recommend interventions with success metrics. Includes statistical significance guidance and domain-specific funnel stages from domain-context.md. Use when someone says "funnel", "conversion", "drop-off", "activation", "onboarding", "churn", "retention", "pipeline", "trial to paid".

Go-to-market launch playbook for a feature, module, or product. Generates cross-functional checklists, enablement timelines, communication plans, and success metrics. Scales from lightweight P2 launches to full P0 GTM motions. Use when someone says "launch plan", "go-to-market", "GTM", "launch playbook", "launch checklist", "feature launch", "product launch", "release planning", "launch readiness", or "launch brief".

Master PM skill router. Lists all available PM skills by category and routes to the right one based on user intent. Use when someone says "help me with PM work", "what PM skills are available", "I need to write a...", or any vague product management request. Entry point for the PM Toolkit plugin.

Customer journey mapping across the full lifecycle: awareness through renewal. Maps actions, touchpoints, emotions, pain points, and opportunities per stage. Domain-aware: includes compliance and onboarding milestones from domain-context.md. Use when someone says "journey map", "customer journey", "user journey", "experience map", "touchpoints", "pain points", "customer experience", "CX mapping".

Jobs-to-be-Done discovery and analysis using Christensen/Ulwick methodology. Three modes: write JTBD interview scripts, extract job statements from transcripts, or prioritize outcomes by importance vs satisfaction. Use when someone says "JTBD", "jobs to be done", "interview script", "customer jobs", "outcome-driven", "what are customers trying to do", "job statements".

Create structured PM meeting notes with decisions, action items, open questions, and parking lot. Works from raw notes, transcripts, or memory. Use when someone says "meeting notes", "action items", "what did we decide?", "summarize this meeting", or "process these notes".

Messaging framework for consistent customer-facing language across all touchpoints. Positioning statements, value pillars, elevator pitches, per-persona and per-competitor messaging. Use when someone says "messaging framework", "positioning statement", "elevator pitch", "value pillars", "how do we talk about this", "sales messaging", "competitive messaging", "product messaging", "positioning", "tagline", "one-liner", "how do we position against".

Build a complete metric hierarchy from North Star through input metrics, health metrics, and counter metrics. Enforces leading + lagging indicators at every level. Includes instrumentation guidance and AARRR/custom framework decomposition. Use when someone says "metric framework", "measurement plan", "KPI hierarchy", "AARRR metrics", "pirate metrics", "health metrics", "counter metrics", "leading indicators", "instrumentation", "analytics plan", or "how do we measure success".

Migration planning skill for platform migrations, data migrations, product consolidations, vendor/API swaps, and compliance-driven migrations. Generates feature parity matrices, data migration plans, go/no-go gate frameworks, customer communication playbooks, and legacy sunset plans. Use when someone says "migration plan", "platform migration", "data migration", "product consolidation", "vendor migration", "API migration", "compliance migration", "feature parity", "cutover plan", "migration readiness", "legacy sunset", "decommission", "strangler fig", "parallel run", or "migration strategy".

Define and validate a North Star metric and its input metric tree for a B2B SaaS product. Uses Sean Ellis criteria for validation. Builds the full metric hierarchy from North Star down to team-level input metrics. Use when someone says "north star metric", "what should we measure", "product metric", "input metrics", "metric tree", "Sean Ellis", "one metric that matters", "how do we know if we're winning", or "product health metric".

Objection handling playbook organized by category. Teaches reps to diagnose the real concern behind the stated objection and respond with evidence, not clever comebacks. Use when someone says "objection handling", "how do we respond when they say", "too expensive", "competitor says", "they have concerns about", "common objections", "sales objections", "objection playbook", "why do we lose deals", "buyer pushback", "handle pricing objection", "they think we're too small".

Full OKR lifecycle: define, refine, check-in, score, and align OKRs across organizational levels. Enforces outcome-over-output writing standards, leading vs lagging KR balance, and strategic alignment mapping. Use when someone says "OKRs", "objectives and key results", "write OKRs", "review our OKRs", "OKR check-in", "score OKRs", "grade OKRs", "mid-quarter review", "OKR alignment", "cascade OKRs", "are our OKRs good", "help me write key results", "quarterly goals", "OKR scoring", "OKR retrospective", or "team objectives".

Design SaaS onboarding flows with time-to-first-value analysis, activation metric definition, and progressive disclosure patterns. Maps current flows, identifies the "aha moment", and designs optimal paths to activation. Use when someone says "onboarding", "time to value", "activation", "first-run experience", "setup wizard", "aha moment", "TTFV", "user activation", "onboarding checklist", "empty states", "progressive disclosure", or "new user experience".

Create an executive one-pager for initiatives and proposals. Structured as: Problem, Approach, Metrics, Timeline, Ask. Maximum one page. Use when someone says "one pager", "executive summary", "initiative brief", "proposal", "I need to pitch this", or "summarize this for leadership".

Teresa Torres Opportunity Solution Tree: outcome, opportunity space, solutions, experiments. Use when someone says "opportunity tree", "OST", "opportunity solution tree", "discovery", "what should we build", "map opportunities", "Teresa Torres", "continuous discovery".

PE board migration progress report generator. Produces a 1-page dashboard for PE operating partners covering ARR migration status, wave progress, synergy realization, risks, and customer health. Designed for busy board members who scan 10-15 portfolio reports per month. Use when someone says "PE report", "migration board update", "PE operating review", "ARR migration status", "synergy report", "portfolio migration update", "board migration progress".

Data-driven persona creation grounded in behavioral patterns, not demographics. Guides you from raw data to validated persona profiles with goals, frustrations, decision criteria, and tools. Use when someone says "persona", "user profile", "who are our users", "customer segments", "target audience", "ICP", "ideal customer profile".

Blameless incident and failure post-mortem generator using 5 Whys root cause analysis. Produces structured post-mortem documents with timeline, contributing factors, corrective actions, and lessons learned. Tracks MTTR and detection time metrics. Use when someone says "post-mortem", "postmortem", "incident review", "root cause analysis", "5 whys", "what happened", "outage review", "failure analysis", "RCA".

Generate a Product Requirements Document (PRD) with four modes: Full PRD for net-new features, Lightweight Feature Spec for sprint-level work, Iteration/V2 Spec for follow-ups on shipped features, and Migration/Compliance Spec for regulatory or API migrations. Enforces problem-first thinking, leading + lagging metrics, non-goals, and testable acceptance criteria. Use when someone says "PRD", "product requirements", "feature spec", "write a spec", "requirements document", "what to build", "engineering spec", "technical requirements", "migration spec", "compliance spec", "V2 spec", or "iteration spec".

SaaS pricing analysis. Covers value metrics, packaging, willingness-to-pay research, competitive positioning, and pricing model design. Use when someone says "pricing strategy", "how should we price this", "packaging", "willingness to pay", "Van Westendorp", "price sensitivity", "monetization", "competitive pricing", "premium tier", "pricing page", "value metric", "Gabor-Granger", "behavioral pricing", "feature shock", "pricing failure", "WTP segmentation", "monetization failure", or "pricing integrity".

SOP and runbook generator for PM processes. Documents steps, decision points, checklists, ownership, and compliance checkpoints. Produces actionable runbooks. Use when someone says "SOP", "standard operating procedure", "runbook", "process doc", "how do we do X", "document the process", "playbook", "checklist", "workflow documentation".

Create a lightweight product brief using Amazon-style working-backwards method. Starts with the customer outcome (press release), then works back to requirements. One page max. Use when someone says "product brief", "working backwards", "PR/FAQ", "pitch this feature", "one-page brief", or "write the press release first".

Full quarter planning: strategic themes, capacity allocation, dependency mapping, bet sizing, and commitment plans. Use when someone says "plan next quarter", "quarterly planning", "Q2 planning", "capacity planning", "what should we build next quarter", "quarter kickoff".

Generate customer-facing release notes from git logs, changelogs, or manual input. Narrative style focused on customer benefit, not feature names. Supports multiple output formats: blog post, email snippet, in-app notification, changelog entry. Use when someone says "release notes", "changelog", "what shipped", "customer update", "release communication", "what's new", "product update email", "in-app notification", "ship log", or "announce this release".

Pre-review quality gate that checks any PM artifact (PRD, strategy doc, one-pager, brief) against Head of Product standards. Scores problem clarity, metrics quality, scope discipline, and compliance awareness. Acts as "the HoP reviewing your work before the real HoP sees it." Use when someone says "review this", "check this PRD", "is this ready for review", "quality check", "does this meet the bar", or "pre-review my spec".

Product risk identification, scoring, matrix plotting, and mitigation planning. Use when someone says "risk register", "risk assessment", "what could go wrong", "risk matrix", "risk mitigation", "identify risks", "risk planning", "risk review".

Generate sales and pitch deck CONTENT — narrative structure, slide-by-slide content, talk tracks, and anticipated objections. NOT visual design. Covers B2B sales presentations, competitive pitches, and demo intros. Use when someone says "sales deck", "pitch deck", "sales presentation", "customer pitch", "demo deck", "prospect presentation", "deal deck", or "competitive pitch".

Sprint retrospective facilitator with Start/Stop/Continue and 4Ls formats. Generates structured retro outputs with action items, owners, and deadlines. Use when someone says "retro", "retrospective", "sprint review", "what went well", "start stop continue", "4Ls", "team reflection", "iteration review".

Simulate how different stakeholders would react to a proposed product change. Surface objections, concerns, and political dynamics before the real meeting. Use when someone says "how will X react?", "stakeholder analysis", "what objections will I face?", "prepare me for the meeting", or "simulate the room".

End-of-quarter strategic review in narrative style with a bets scorecard. Use when someone says "quarter review", "strategic review", "what happened last quarter", "quarterly retro", "bets scorecard", "review our bets", "end of quarter report".

SWOT analysis with structured strategic implications and SO/ST/WO/WT options. Use when someone says "SWOT analysis", "strategic analysis", "competitive position", "strengths and weaknesses", "market analysis", "where do we stand".

Strategyzer Value Proposition Canvas: customer profile, value map, and fit analysis. Use when someone says "value proposition", "value prop canvas", "customer jobs", "jobs to be done", "pain points", "why do customers buy us", "product-market fit".

Structure and analyze win/loss data. Two modes: generate interview guides for win/loss calls, or analyze existing data to identify patterns and recommendations. Covers competitive analysis, decision factors, and segment-level insights. Use when someone says "win loss", "win/loss analysis", "why did we lose", "deal analysis", "competitive win rate", "lost deal review", "churn analysis", "win loss interview", or "why did we win".

Multi-skill workflow that produces a complete competitive intelligence package. Chain: (1) SWOT analysis, (2) Market sizing via web research, (3) Competitive profiles, (4) Positioning analysis, (5) One-pager summary. Uses web search to gather real competitive data. Outputs a comprehensive competitive brief. Use when someone says "competitive analysis", "competitive intel", "competitor research", "market analysis", "how do we compare", "competitive landscape", "market positioning".

Multi-skill workflow that produces a complete migration execution package. Chain: (1) Migration PRD, (2) Migration Planner, (3) Risk Register, (4) Stakeholder Simulation, (5) Comms + PE Report. Each stage produces an artifact that feeds the next. Designed for platform migrations, product consolidations, and post-acquisition integrations. Use when someone says "migration workflow", "migration plan end to end", "consolidation workflow", "post-acquisition migration", "platform migration plan", "full migration package", "migration execution plan", "M&A integration workflow".

Multi-skill workflow chain that takes a raw problem statement and produces a complete PRD. Chain: (1) JTBD extraction, (2) Persona generation, (3) Opportunity tree mapping, (4) Feature spec / PRD generation, (5) Quality review. Each stage produces an artifact that feeds the next. Shows progress between stages. Use when someone says "problem to PRD", "build a PRD from scratch", "full spec workflow", "take this problem and write a PRD", "end-to-end spec", "problem to solution".

Multi-skill workflow that runs the full quarterly planning cycle. The "big one." Chain: (1) Strategic review of past quarter, (2) North star validation, (3) OKR definition, (4) Quarterly planning with capacity and bets, (5) Roadmap generation. Each stage builds on the previous. Complete quarterly planning ceremony. Use when someone says "quarterly planning", "Q[N] planning", "quarterly cycle", "next quarter", "planning ceremony", "OKRs", "roadmap planning", "quarterly review".

Multi-skill workflow that produces a complete sales enablement package. Chain: (1) Messaging framework, (2) Competitive battlecards, (3) Objection playbook, (4) GTM launch playbook. Each stage produces an artifact that feeds the next. Outputs are written for revenue teams, not product teams. Use when someone says "sales enablement", "enable the sales team", "sales toolkit", "go-to-market package", "competitive sales materials", "arm the sales team", "sales readiness", "launch enablement pack".