Product & Strategy

Quarterly re-scan of a prior PESTEL analysis. Use when checking which macro factors moved, which assumptions broke, and what's new — turning PESTEL from a workshop artifact into a radar.

Build an evidence-cited SWOT of one company — yours or a competitor's — from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor depth.

Mine public reviews, app stores, and forums for unmet needs, competitor weaknesses, and switching triggers — with quoted evidence. Use when you want customer voice without waiting on interviews.

Research a competitive landscape with cited snapshots, a comparison matrix, and so-what implications. Use when a product decision needs competitive grounding, not a market report.

Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool. Use when weighing market entry or when margins erode and nobody can say why.

Map a market's segments, players, substitutes, and whitespace with cited evidence. Use when entering or re-evaluating a market before sizing, positioning, or picking competitors to study.

Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.

Scheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.

Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.

Track competitor pricing and packaging as a diffable time series. Use when monitoring tiers, gates, limits, and price moves on a monthly or quarterly cadence.

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.

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.

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.

The protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs.

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

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.

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

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.

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.

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

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

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

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.

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

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.

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

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.

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

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

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

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

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

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.

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.

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.

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

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.

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.

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

Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.

Run a product sunset end to end — decide, align, plan, prepare, announce, close. Use when you need the whole EOL process, not just one artifact.

Build a phase-gated EOL checklist sized to the sunset, with a named owner on every item. Use when the decision to retire is made and you need the operational plan.

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.

Plan who to talk to about a sunset, in what order, and what each conversation must cover. Use when an EOL decision is made and you want the landmines found before the announcement.

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.

Run a go/no-go assessment for retiring a product or feature, then right-size the effort. Use when someone says "we should probably kill this" and nobody has made the call.

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.

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.

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

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.

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.

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

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.

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

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.

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

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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.

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

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

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

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

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.

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

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.

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.

63 plug-and-play PM skills for AI agents: 30 Triple Diamond phase + 8 foundation + 10 utility + 15 tool (Foundation Sprint + Design Sprint). Plus 4 sub-agents, templates, workflows, samples, CI-enforc

Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.

Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated…

Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers).

Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes.

Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe…

Walk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, G4 post-tag hygiene) via the…

Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying…

Scores completed OKR sets at cycle close with KR-level scoring per the canonical OKR type enum (committed | aspirational | learning | operational_health | compliance_or_safety)…

Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch).

Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations.

Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits.

Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market…

Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate…

Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact.

Day 5 (Friday) sprint-closing move of a Design Sprint that produces the bundled Friday artifact covering per-customer interview observations, best quotes, scorecard grid (sprint questions by…

Day 2 morning move of a Foundation Sprint. Forces generation of 3 to 7 candidate approaches as one-page summaries before the team converges on a top bet.

Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.

Day 4 (Thursday) move of a Design Sprint that produces the planning artifact for the day. Output covers the prototype role plan (Maker, Stitcher, Writer, Asset Collector, Interviewer), prototype…

Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions.

Teaches PMs to create syntactically valid mermaid diagrams by selecting the right diagram type for their communication need, following syntax validity rules, and validating before shipping.

Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for.

Run a repo-wide cross-cutting governance audit via the pm-skill-auditor sub-agent. Aggregates the enforcing validator suite, re-derives aggregate counters, and surfaces cross-cutting issues no single…

Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied.

Run adversarial review on a PM artifact via the pm-critic sub-agent. Returns findings graded P0/P1/P2/P3 with a concrete fix suggestion per finding and a machine-readable status block.

Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert…

Day 3 (Wednesday) move of a Design Sprint that runs the art museum layout, heat map, speed critique, straw poll, Decider supervote, rumble-vs-all-in-one decision, and the storyboard that drives…

Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting.

Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation.

Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable…

Creates a structured lessons learned entry for organizational memory. Use after an incident, a completed project, or a significant learning to record knowledge for future teams and initiatives.

Specifies what analytics events to track, when they fire, and what properties to include, as a contract between product and engineering that prevents undertracked features.

67 plug-and-play, best-practice, product management skills for AI agents: 30 Triple Diamond phase + 8 foundation + 10 utility + 15 tool (Foundation Sprint + Design Sprint)... Plus 4 sub-agents, templa

Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first.

Pre-sprint brief that locks scope, the decision the sprint must unlock, team and role assignments, logistics, inputs to bring, and success criteria before Day 1 of a Foundation Sprint.

Day 1 morning move of a Foundation Sprint. Forces explicit team choices on target customer, important problem, team advantage, and competitors and alternatives.

Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference.

Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a…

Day 1 afternoon move of a Foundation Sprint. Converts the morning's Basics frame into a defensible strategic position by scoring differentiator candidates against customer-perceived value, choosing…

Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach.

Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…

Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent.

Day 2 afternoon move of a Foundation Sprint. Evaluates the candidate approach set through multiple lenses (4 classic plus at least 1 custom) to surface trade-offs, identify consistent winners and…

Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions.

Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices.

Creates a structured competitive analysis comparing features, pricing, and positioning across 3-5 direct and indirect competitors, with a 2x2 map and actionable strategic recommendations.

Pre-sprint diagnostic that determines whether a team should run a Design Sprint now, postpone it, or do prerequisite work first.

Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language.

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured.

Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives.

Estimate market opportunity (TAM, SAM, SOM) using multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market).

Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart.

Analyze survey results into actionable PM insights. Produces persona segmentation, hypothesis validation status, thematic clustering of open-text responses, statistical confidence labels, prioritized…

Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is…

Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

66 plug-and-play, best-practice, product management skills for AI agents: 30 Triple Diamond phase + 8 foundation + 10 utility + 15 tool (Foundation Sprint + Design Sprint)... Plus 4 sub-agents, templa

Designs an A/B test or experiment with variants, success metrics, sample size, and duration for an existing hypothesis.

Documents the results of a completed technical or design spike, capturing the original question, approach, evidence-backed findings, and a clear proceed-or-not recommendation so the team does not…

Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs.

Produces a topic-segmented post-meeting summary for attendees with decisions highlighted and actions captured inline per topic (plus a consolidated action view at the end).

Generates an evidence-calibrated product or marketing persona using the canonical v2.5 output contract.

Drafts, reviews, rewrites, and coaches outcome-based OKR sets across team, department, product, or company scopes.

Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences.

Produces a one-page lean canvas across nine interlocking blocks (problem, customer, UVP, solution, channels, revenue, cost, metrics, unfair advantage) with optional inline HTML and SVG visual…

Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made.

Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step.

67 plug-and-play, best-practice, product management skills for AI agents: 30 Triple Diamond phase + 8 foundation + 10 utility + 15 tool (Foundation Sprint + Design Sprint)... Plus 4 sub-agents, templa

Skill from aakashg: competitive-analysis

Skill from aakashg: sprint-planner

Skill from aakashg: user-research

Bad: "Make sure everything works" Good: "Verify signup flow completes end-to-end in staging (email → verification → first dashboard load).

The PRD isn't dead. The bad PRD is dead. AI killed the 10-page PRD — no one read those. The modern PRD is lighter, sharper, and example-heavy. The PRD evolves through stages.

Skill from aakashg: metrics-definer

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing.

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output.

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues.

Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR.

Analyze any product's strategy, UX decisions, business model, and growth loops. Use when a user wants to understand how a product works and why.

Turn git commits, tickets, or raw notes into user-facing release notes. Adjustable tone (B2B formal, B2C friendly, internal).

Generate a 1-page meeting brief with context, objectives, key questions, pre-read, expected decisions, and a parking lot. Takes a meeting topic or agenda and outputs a structured prep document.

Turn raw notes into a polished stakeholder update. Supports email, Slack message, or deck bullet points.

Generate a complete user research brief with hypotheses, interview guide, and open-ended questions. Takes a research topic or hypothesis and returns a ready-to-use interview kit.

Translate a technical document (API spec, architecture doc, RFC, eng proposal) into PM-friendly language. What it means for the product and users.

Turn a feature description into well-structured user stories with acceptance criteria, edge cases, and dependencies.

Facilitate a team retrospective. Generate a retro board with prompts (4Ls, Start-Stop-Continue, Sailboat formats) or synthesize retro notes into grouped themes and prioritized action items.

Transform a list of priorities, features, or initiatives into a structured product roadmap. Now/Next/Later format with dependencies, effort sizing, and strategic rationale.

Design a complete A/B test or experiment from a hypothesis. Takes what you want to test and outputs a full experiment design with hypothesis, metrics, sample size, duration, and success criteria.

Generate a concise, structured PRD from a product idea. NOT a 20-page doc — 1-2 pages that force clarity.

Analyze product data from a CSV file or pasted data. Finds trends, anomalies, segments, and actionable insights. Ask questions about your data in plain English.

Generate a complete go-to-market checklist from a product description. Everything you need to launch.

Classify and analyze raw user feedback into themes, sentiment, and actionable insights. Takes pasted feedback text or a path to a CSV file and returns structured patterns and recommendations.

TAM/SAM/SOM estimation for any product or market. Takes a product/market description and returns structured market sizing with sources, assumptions, and confidence ranges.

Generate actionable user personas from a product description, user data, or research notes. Not marketing fluff — behavioral personas that drive product decisions.

Score and prioritize a list of features or initiatives using RICE, ICE, or custom frameworks. Takes a feature list and outputs a ranked table with rationale and a recommended cut line.

Turn business goals into structured OKRs with measurable Key Results, linked initiatives, alignment check, and anti-goals. Takes a strategic priority and outputs ready-to-use OKRs.

Quick competitive landscape scan for any product or market. Takes a product/market description and returns a competitive map with positioning, gaps, and opportunities.

Structure a product decision with options, trade-offs, and a clear recommendation. Takes a decision to make and outputs a concise decision document ready for stakeholder review.

Conduct a comprehensive competitive landscape analysis including competitor profiling, value chain mapping, positioning maps, and whitespace identification.

Assess the defensibility of a product or company across 8 moat types, grounded in habit-forming product theory, the Fogg Behaviour Model, and aggregation theory.

Analyze a product's value chain and ecosystem strategy using aggregation theory, identifying integration opportunities and portfolio coherence.

Verify the quality and completeness of any PM strategy artifact before sharing with stakeholders. Re-reads the document and validates against a structured checklist.

Skill from aniganti: using-pm-superpowers

Framework-driven feature and initiative prioritization using RICE, ICE, or weighted scoring. Grounds prioritization in strategic pillars and demands evidence-based scoring.

A generative AI prompt builder for product managers. Walks PMs through 9 guided questions to craft structured, effective prompts for any AI assistant.

Conduct a VRIO (Value, Rarity, Imitability, Organization) analysis to assess competitive advantages of a product or company.

Interactive 6-step product strategy framework grounded in Rumelt's strategy kernel (Why/What/How). Guides PMs through market analysis, problem definition, strategic pillars, design and technical…

Prepare tailored stakeholder briefing documents, audience-specific FAQs, and workshop agendas to build alignment on product strategy.

Capture and track product decisions with structured reasoning, alternatives considered, and evidence. Builds institutional memory and prevents re-litigation of settled decisions.

Pre-mortem risk analysis for product launches. Identifies Tigers (real risks), Paper Tigers (overblown concerns), and Elephants (unspoken worries) to improve launch readiness.

Build a quarterly roadmap from prioritized features. Considers team capacity, dependencies, and strategic goals. Outputs a now/next/later or time-based plan with rationale.

Generate multi-audience stakeholder updates tailored for engineering, leadership, and customer-facing teams, pulling context from knowledge files and MCP integrations.

Review product metrics, identify trends and anomalies, connect movements to OKRs and recent changes, and produce actionable recommendations.

Guided OKR creation with strategy alignment. Reads existing strategy, helps craft objectives and measurable key results, and validates quality and alignment.

Codebase-aware technical feasibility assessment. Scans existing code for reusable components, estimates complexity with T-shirt sizing, identifies risks, and flags areas needing engineer input.

Product Manager's Operating System: gateway skill that routes requests to 27 PM workflow skills and manages the knowledge system.

Generate meeting preparation docs tailored by meeting type, pulling context from past meetings, recent decisions, action items, and sprint status.

Score and rank features using RICE or ICE frameworks. Aligns with OKRs for strategic weighting. Outputs a ranked list with scores, rationale, and top recommendations.

End-to-end quarterly planning. Reviews past performance, reads strategy and capacity, then produces quarter themes, OKRs, roadmap commitments, resource allocation, and risk assessment.

Generate a complete PRD through guided discovery, context alignment, and optional codebase analysis. Outputs a populated spec with user stories, Gherkin acceptance criteria, metrics, and launch plan.

Research a competitor from their URL or name. Fetch website, pricing, features, and news. Generate a battlecard with positioning, strengths, weaknesses, and strategic implications.

Generate a comprehensive launch checklist from a PRD, covering release criteria, QA, comms, rollback, metrics, and stakeholder prep. Slash command: /launch <feature>

Facilitate structured retrospectives and post-mortems with probing questions, timeline construction, root cause analysis, and recurring theme detection across past retros.

Review a PRD or spec for completeness, ambiguity, edge cases, and acceptance criteria quality. Present structured findings by severity and offer to fix issues directly.

Morning briefing for PMs. Reads all knowledge files, pulls from MCPs, and produces a prioritized "what matters today" summary. Slash command: /brief

Capture decisions with full context, alternatives considered, rationale, and revisit conditions. Auto-links to related PRDs, strategy docs, and OKRs.

User research interview guide creation. Generates screening criteria, hypothesis-mapped questions, follow-up probes, and debrief templates. Includes guidance on avoiding bias.

Analyze customer feedback from any source. Categorize by theme, frequency, and severity. Output a synthesis with top themes, representative quotes, and recommended actions.

Create beautiful HTML slide decks for product presentations. Reads product context, extracts brand colors from websites, and generates self-contained HTML files with keyboard navigation and…

Interactive user persona creation. Researches audiences via web, builds detailed persona profiles with demographics, behaviors, and motivations, and links personas to product features and user…

Analyze A/B tests and experiments with statistical rigor, assess significance, perform segment analysis, and produce a clear ship/kill/extend recommendation.

Reads all knowledge files and MCP integrations to produce a single-page product status dashboard with OKR progress, sprint status, decisions, blockers, launches, and metrics.

Interactive onboarding wizard that creates the PM-OS knowledge base for your product. Asks questions, fetches company info, and populates all knowledge files.

End-to-end user journey mapping. Maps stages from awareness through advocacy, identifies actions, thoughts, emotions, pain points, and opportunities at each stage.

Interactive strategy document creation. Reads company context, researches competitors and market trends, then generates a comprehensive product strategy with vision, pillars, positioning, and metrics.

Sprint planning with capacity awareness. Pulls from backlog (via MCP or manual input), calculates what fits based on team velocity, and outputs recommended scope with stretch goals and deferred items.

Validate ideas with market sizing (TAM/SAM/SOM), competitive landscape, strategic alignment, technical feasibility, and a go/no-go recommendation.

Business strategy and positioning wisdom from 150+ Lenny's Podcast episodes. Covers competitive positioning, market analysis, pricing strategy, category design, and strategic decision-making.

Career development wisdom from 190+ Lenny's Podcast episodes. Covers career growth, job searching, negotiation, skills development, networking, and personal branding.

Product management wisdom from 200+ Lenny's Podcast episodes. Covers discovery, delivery, prioritization, roadmaps, metrics, OKRs, and PM frameworks.

Startup and entrepreneurship wisdom from 160+ Lenny's Podcast episodes. Covers founding, fundraising, scaling, pivoting, product-market fit, and building companies.

Leadership and management wisdom from 180+ Lenny's Podcast episodes. Covers team building, hiring, culture, feedback, 1:1s, performance management, and scaling organizations.

Growth and marketing strategies from 140+ Lenny's Podcast episodes. Covers user acquisition, retention, engagement, virality, PLG, monetization, and growth loops.

AI product development wisdom from 120+ Lenny's Podcast episodes. Covers AI product strategy, LLM applications, ML integration, AI agents, and building AI-native products.

Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles".

Use when asked to "run a design sprint", "5-day sprint", "prototype in a week", "test ideas before building", or "Jake Knapp sprint". Helps teams go from problem to tested prototype in five days.

Use when asked to "run an A/B test", "design an experiment", "check statistical significance", "trust our results", "avoid false positives", or "experiment guardrails".

Use when asked to "working backwards", "PR/FAQ", "Amazon PR/FAQ", "write a press release", "define a new product", or "write a customer-focused PRD".

Use when asked to "product-led SEO", "programmatic SEO", "build programmatic pages", "organic acquisition for product", "decide if SEO is worth it", or "optimize for AI search".

Use when asked to "build habit-forming products", "Hooked model", "trigger action reward investment", "create sticky behavior loops", or "design habit loops".

Use when asked to "strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", or "movement narrative".

Use when asked to "PMF survey", "measure product-market fit", "40% rule", "Sean Ellis test", "Rahul Vohra method", or "how disappointed would you be".

Use when asked to "7 Powers", "build a competitive moat", "analyze defensibility", "find sustainable advantage", "economic moats", or "Hamilton Helmer framework".

Use when asked about "pricing strategy", "willingness to pay", "value metric", "packaging tiers", "good better best pricing", "subscription vs usage pricing", or "price before product".

Use when asked to "radical candor", "give feedback that cares", "have a difficult conversation", "challenge directly", "manage performance issues", or "give praise that lands".

Use when asked to "opportunity solution tree", "OST", "Teresa Torres", "map customer opportunities to outcomes", "structure discovery around opportunities", or "compare solutions for a customer…

Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions".

Use when asked to "define our core action", "North Star metric", "accruing benefits", "improve retention mechanics", "hierarchy of engagement", or "Sarah Tavel framework".

Use when asked to "jobs to be done", "JTBD", "why customers churn", "prep for customer interviews", "hire and fire products", or "find real competitors".

Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs".

Use when asked about "marketplace strategy", "chicken and egg problem", "liquidity", "two-sided market", "tipping a marketplace", "GMV growth", or "Sarah Tavel marketplaces".

Use when asked to "growth loops", "build a growth engine", "design a viral loop", "create a content loop", "move beyond paid acquisition", or "why isn't growth compounding".

Use when asked to "position my product", "positioning canvas", "differentiate from competitors", "figure out our category", "repositioning", or "why customers should pick us".

Use when asked about "product-led growth", "PLG strategy", "self-serve growth", "freemium model", "free trial design", "product-led sales", "PQL", or "bottoms-up growth".

A 3-stage practice for clarifying a hard product decision — translate stakeholder asks into the actual problems underneath, stress-test those problems, then pick what matters.