flywheel-pm

Check a product decision against cognitive biases most likely to affect your judgment right now

Generate stakeholder-specific alignment narratives using proven buy-in techniques

Capture learnings from a product cycle and update your PM profile — the most important step

Set up and update your work context — company priorities, team capacity, customer signals, competitive landscape

Frame a decision explicitly with options, criteria, trade-offs, reversibility, and stakeholders before committing

Analyze competitive differentiation using 7 Powers, unique assets, and segment-specific advantages

Create a structured friction log for any product flow — categorize, score, and pattern-match friction

Set team goals by connecting team-level metrics to the North Star Metric

Design and analyze growth loops — acquisition, engagement, monetization, and viral mechanics

Prepare interview guides, capture structured notes, and extract patterns from customer conversations

Full autonomous PM workflow — from idea to spec-ready with learnings captured

Create a comprehensive measurement framework with predictions for post-launch tracking

Map the full adoption equation for a feature — motivation, friction, nudge, and satisfaction

Design your North Star Metric with ecosystem analysis, guardrails, and team goals

Create your personalized PM profile through import or interactive Q&A

Transform a raw insight or idea into a structured, evaluated opportunity

Generate a weekly/biweekly product review covering shipped work, metrics, decisions needed, and learnings

Ingest and synthesize customer signals from multiple sources — support tickets, NPS, feature requests, sales notes, usage data

Analyze retention with cohort curves, habit loops, and resurrection strategies

Multi-agent review of a product spec from different PM perspectives

Riff on product news, launches, or announcements from multiple strategic angles — builds product sense and strategic thinking muscle

Create needs-based user segments using motivations and behaviors, not demographics

Share a learning, pattern, or framework with your PM team's shared knowledge base

Simulate how each user segment will actually react to a product change before shipping it

Design and evaluate solution approaches for an identified opportunity

Transform a solution into a detailed, actionable product specification — from solution docs or via structured interview

Build a complete product strategy — segmentation, differentiation, strategic pillars, non-priorities, and roadmap

Guided product teardown that trains simulation muscle — practice modeling how users think, feel, and act

Structure and resolve product tradeoffs with clear criteria, evidence, and reversibility analysis

Apply behavioral design principles and cognitive psychology to a specific product flow

What Are You Really Trying To Do? — peel back feature requests to find the real underlying need

Guided first-run experience for new PMs — takes you from install to your first compounded cycle

Proactively detects cognitive biases in product decisions, opportunity evaluations, and specs. Use to surface biases before they distort decisions.

Reviews teardowns and simulations for blind spots, bias patterns, and simulation accuracy. Use when evaluating a PM's product analysis for cognitive gaps.

Research competitive positioning, recent moves, and market context for opportunity evaluation. Use during /pm:opportunity to understand the competitive dimension.

Analyzes growth loops, retention curves, and viral mechanics. Use when evaluating growth strategy, diagnosing retention problems, or validating growth model assumptions.

Searches past opportunities, compounds, and PM profile for similar past bets. Surfaces what worked, what failed, and what patterns exist. Use during opportunity evaluation.

Analyzes PM documents (decks, operating systems, past specs) to extract frameworks, vocabulary, and patterns for the PM profile. Use during /pm:onboard import mode.

Analyzes multiple customer interviews and signal reports to extract cross-cutting patterns, frequency counts, and confidence levels. Use when synthesizing research from multiple sources.

Reviews the business case, revenue quantification, pricing decisions, and strategic fit of product specs. Use when validating that a feature makes business sense before committing resources.

Reviews product specs from the customer's perspective. Validates problem framing, user journey completeness, and whether the solution actually addresses the stated pain. Use when reviewing specs before engineering handoff.

Reviews metrics frameworks for completeness, measurability, and alignment. Checks activation funnels, engagement definitions, and whether Continue/Pause/Pivot criteria are specific enough. Use when validating measurement plans.

Searches past opportunities, specs, and compound docs to find similar patterns. Surfaces past learnings, successful approaches, and mistakes to avoid. Use during spec review or opportunity evaluation.

Detects scope creep, unnecessary complexity, and features disguised as must-haves. Ensures the spec solves one problem well instead of three problems poorly. Use during spec review.

Reviews product strategy documents for completeness, differentiation, and intellectual honesty. Use when reviewing strategy docs before sharing with stakeholders.

North Star Metrics, ecosystem analysis, goal-setting, and tradeoff frameworks. Use when defining metrics, setting team goals, or resolving product tradeoffs.

Apply behavioral psychology, UX principles, and decision science to product design. Use when designing user flows, evaluating UX quality, or diagnosing adoption problems.

Growth loops, retention frameworks, viral mechanics, and acquisition models. Use when designing growth engines, diagnosing retention problems, or evaluating acquisition strategies.

Design complete metrics frameworks with outcome-intermediate-leading hierarchy, activation funnels, and engagement dimensions. Use when defining how to measure product success.

Evaluate product opportunities using the 5-question customer problem framework, business context analysis, and prioritization matrices. Use when assessing whether an idea is worth pursuing.

Load and apply the PM's personalized operating system from pm-profile.yaml. Use when any /pm: command needs to adapt to the PM's frameworks, vocabulary, and past patterns.

Explore product news, launches, and announcements from multiple strategic angles to build product sense. Use when riffing on industry news, analyzing competitor moves, or training strategic thinking muscle.

Cognitive empathy engine — simulation, metacognition, and intellectual flexibility for product decisions. Use when modeling user behavior, checking assumptions, or developing product intuition.

Apply 20 systematic creativity techniques to generate solution candidates for product opportunities. Use when brainstorming solutions or feeling stuck on approaches.

Create comprehensive product specs through structured AskUserQuestion interviews or review existing specs against a detailed completeness checklist. Use when creating specs from scratch (no solution doc) or reviewing spec quality.

Apply proven buy-in techniques to align stakeholders on product direction. Covers framing, social proof, goal seek, inception, citation, and narration. Use when building alignment for initiatives.

Segmentation, differentiation, and strategic thinking frameworks. Use when building product strategy, analyzing competition, or making strategic bets.

Write compelling 3-part vision narratives that are detailed, opinionated, and user-centric. Use when creating spec narratives or stakeholder presentations.