Competitive Teardown
Produce a structured competitive analysis of a rival product or company, focused on strategy and positioning rather than feature checklists. Use when the user says "tear down [competitor]", "competitive analysis", "how do we compare to X", "what is [company]'s strategy", or asks to analyze a competitor's launch or pricing.
Launch Plan
Build a go-to-market launch plan with tiering, owner matrix, timeline, and go/no-go checklist. Use when the user says "plan this launch", "GTM plan", "launch checklist", "release plan for [feature]", or is preparing to ship something to customers.
Prd
Draft a product requirements document (PRD) from a rough idea, feature request, or problem statement. Use when the user says "write a PRD", "spec this out", "draft requirements", "product spec", or shares a feature idea they want documented for engineering and design.
Stakeholder Comms
Draft the hard workplace messages product managers must send — saying no to a feature request, announcing a delay or de-scope, escalating a blocker, pushing back on an executive, or delivering unwelcome findings. Use when the user says "help me tell X that", "how do I say no to", "announce this delay", "escalate this", or "push back on".
Experiment Design
Design an A/B test or product experiment with a falsifiable hypothesis, guardrail metrics, sample-size sanity check, and pre-committed decision rules. Use when the user says "design an experiment", "A/B test for", "how should we test this", "is this result significant", or wants to validate a product change with data.
Exec Update
Write a concise executive status update or weekly memo in SCR (Situation-Complication-Resolution) style. Use when the user says "write my exec update", "status update for leadership", "weekly update", "steering committee summary", or shares raw notes about project progress to be turned into an upward-facing memo.
Release Notes
Write customer-facing release notes and changelog entries from commit logs, merged PRs, ticket lists, or internal change descriptions. Use when the user says "write release notes", "changelog for this release", "announce these changes", or shares a list of shipped changes needing customer-facing copy.
Prioritize
Score and rank a backlog of features, projects, or bets using RICE, ICE, or opportunity-cost framing, and write the tradeoff memo that defends the ranking. Use when the user says "prioritize", "stack rank", "what should we build first", "RICE score", or shares a list of competing initiatives.
Metrics Tree
Define a north-star metric, decompose it into a driver tree, and produce an instrumentation spec engineers can implement. Use when the user says "define metrics for", "what should our north star be", "build a metrics tree", "KPI framework", or "what should we measure".
Roadmap
Build a Now/Next/Later product roadmap organized by themes with confidence levels and kill criteria. Use when the user says "build a roadmap", "roadmap for next quarter/half/year", "now next later", or needs to turn a strategy and backlog into a communicable plan.
Feedback Triage
Classify and rank a pile of raw customer feedback — support tickets, app reviews, NPS verbatims, sales notes, survey responses — into themes with counts, severity, and recommended actions. Use when the user says "triage this feedback", "what are customers complaining about", "analyze these reviews/tickets", or shares a feedback export (CSV, text dump).
Story Splitter
Split an epic, feature, or PRD into user stories with acceptance criteria, sized for iterative delivery. Use when the user says "split this epic", "break this down into stories", "write user stories", "acceptance criteria for", or shares a spec that needs to become a sprint-ready backlog.
User Interviews
Synthesize raw user interview notes, call transcripts, or research sessions into themes, evidence, and product implications. Use when the user says "synthesize these interviews", "analyze this transcript", "what did users tell us", "research synthesis", or shares interview notes or call recordings' transcripts.