Prd Writer
Write comprehensive Product Requirement Documents from research. Use when you've validated a problem and solution, and need to align engineering, design, and stakeholders on what to build.
Ab Test Reader
Interpret A/B test results with confidence. Use when reviewing A/B test results and need to distinguish signal from noise.
Experiment Analysis
Analyze experiment data and draw conclusions. Use when an A/B test or product experiment has concluded and you need to interpret the results.
Prototype Planning
Plan what to prototype and at what fidelity. Use when you want to test a solution idea without building the full product.
Solution Brainstorming
Structured ideation with constraints. Use when generating solution ideas for a defined problem or opportunity, getting a team unstuck, or finding creative approaches.
Go To Market
GTM strategy for new features or products. Use when preparing to launch something new and need a coordinated plan across product, marketing, sales, and support.
Adoption Funnel
Analyze and improve feature adoption. Use when a feature isn't getting the usage you expected and you need to understand why.
Retrospective
Structured retros using Start/Stop/Continue, 4Ls, or Sailboat. Use after a launch, sprint, or project to learn what worked and what to improve.
Acceptance Criteria
Write clear, testable acceptance criteria using Given/When/Then format. Use when defining user stories, testing requirements, or creating a Definition of Done.
Dashboard Design
Design metric dashboards that drive action. Use when building or improving a dashboard for your product, team, or stakeholders.
User Story Writer
Write user stories with INVEST criteria and acceptance criteria. Use when breaking down features into developer-ready units of work.
Churn Analysis
Diagnose churn and identify retention levers. Use when customers are leaving and you need to understand why and how to keep them.
Problem Statement
Frame the customer problem with evidence before jumping to solutions. Use when starting a new initiative, aligning stakeholders, or writing a PRD.
Validation Interview
Test prototypes and concepts with customer interviews. Use when you have a solution concept or prototype and need to validate assumptions before building.
Stakeholder Communication
Status updates, exec briefs, and dashboards for stakeholders. Use when reporting progress, managing expectations, or communicating risks to leadership.
Launch Plan
End-to-end launch checklists and timing. Use when preparing to ship a feature or product to ensure all cross-functional work is coordinated.
North Star Metrics
Define and align around North Star metrics. Use when choosing or refining the primary metric that drives product decisions.
Iteration Prioritization
Prioritize post-launch improvements. Use when deciding what to work on next after shipping a feature or product.
Proto Persona
Create hypothesis-driven personas before full research. Use when starting a new product area, aligning on target users, or prioritizing features without existing persona research.
Product Discovery Sprint
End-to-end product discovery sprint over 1-2 weeks. Use when entering a new problem space, preparing for a major initiative, or before committing to a solution.
Feature Ship Cycle
End-to-end feature delivery from PRD to launch measurement. Use when taking a validated concept through specification, development, launch, and post-launch evaluation.
User Research
Synthesis of qualitative and quantitative user research. Use when planning a research study, synthesizing findings, or building a research repository.
Customer Interviews
Plan and conduct customer discovery interviews. Use when exploring a problem space, validating assumptions, or talking to users for the first time.
Product Health Review
Weekly product health check across metrics, user feedback, support trends, and active projects. Use weekly to keep a pulse on product performance.
Jobs To Be Done
Understand customer goals using the Jobs-to-be-Done framework. Use when analyzing user motivation, defining product strategy, or identifying unmet needs.
Elevator Pitch
One-sentence value propositions using Geoffrey Moore's format. Use when defining product positioning, writing a landing page, or pitching to stakeholders.
Epic Breakdown
Split large epics into deliverable stories using proven patterns. Use when an epic is too large for a single sprint and needs to be broken into smaller, independent stories.
Hypothesis Prioritization
RICE, ICE, and value-effort quadrant prioritization. Use when choosing which solution to build first or which experiment to run next.
Feedback Analysis
Synthesize user feedback into actionable insights. Use when collecting feedback from multiple channels and need to find patterns and prioritize improvements.
Quarterly Planning
Strategic quarterly planning connecting company goals to product initiatives. Use at the end of each quarter to plan the next quarter's product work.
Experiment Design
Design lightweight experiments to validate assumptions. Use when you have a hypothesis to test but don't yet have enough evidence to commit to building.
Problem Framing
Reframe problems to unlock better solutions. Use when a team is stuck, stakeholders disagree on approach, or the obvious solutions aren't working.
Release Notes
Write release notes for different audiences. Use when shipping a release and need to communicate changes to end users, enterprise customers, or internal teams.
Metrics Framework
AARRR, HEART, and custom metric trees. Use when defining how to measure product success or building a measurement system.
Opportunity Solution Tree
Map opportunities to potential solutions using Teresa Torres's framework. Use when exploring problem spaces, deprioritizing solutions, and connecting user needs to product decisions.
Market Sizing
TAM/SAM/SOM estimation with top-down and bottom-up approaches. Use when sizing a market opportunity, building a business case, or estimating revenue potential.
Competitive Analysis
Deep-dive competitive positioning analysis. Use when entering a new market, positioning a product, or understanding the competitive landscape.
Technical Spec Bridge
Translate PRDs for engineering audiences. Use when writing technical specifications, defining API contracts, or bridging product requirements to engineering execution.
Rollout Strategy
Phased rollout plans with rollback. Use when deploying a change that has risk and needs controlled exposure before full release.