I'm writing a PRD for [feature name]. The problem we're solving is [problem statement]. Our target users are [user segment]. Key constraints include [technical/business constraints]. Draft a PRD that includes: problem statement, goals and non-goals, user stories, success metrics, proposed solution with key flows, edge cases, and open questions. Use a structured format with headers.

I conducted [number] user interviews about [topic/feature area]. Here are my raw notes: [paste notes]. Analyze these interviews and provide: (1) Top 5 themes ranked by frequency, (2) Direct quotes that best represent each theme, (3) Surprising or contradictory findings, (4) Recommended next steps for product decisions, (5) Gaps in the research that need further investigation.

Our [metric name] changed from [old value] to [new value] over [time period]. Here's what we know: [context — recent launches, seasonality, external factors]. Help me build a hypothesis tree for what could be driving this change. For each hypothesis, suggest: (1) How to validate or invalidate it, (2) What data I should pull, (3) Specific SQL queries or analytics checks I should run, (4) Expected timeline to reach a conclusion.

I need to prioritize these product initiatives for next quarter: [list initiatives]. Our company goals are [OKRs/objectives]. Our team has [number] engineers and [number] designers. Score each initiative on: (1) Impact on key metrics, (2) Strategic alignment, (3) Engineering effort estimate, (4) User demand signals, (5) Risk level. Present as a ranked table with rationale for the top 3 recommendations.

Write a stakeholder update email for [audience: executives/board/cross-functional team]. Context: We're [current sprint/phase] of [project name]. Key updates: [list updates]. Blockers: [list blockers]. Decisions needed: [list decisions]. Format it as a scannable email with a TL;DR at the top, color-coded status indicators (green/yellow/red), and clear asks with owners and deadlines.

Analyze [competitor name] as a competitor to our product [your product]. Compare us across these dimensions: (1) Target audience and positioning, (2) Core feature set and key differentiators, (3) Pricing model and packaging, (4) Recent product launches and strategic direction, (5) Strengths we should respect, (6) Weaknesses we can exploit. End with 3 specific product recommendations based on this analysis.

We're exploring solutions for this user problem: [problem statement]. Our users are [persona description]. Constraints: [technical, business, or timeline constraints]. Generate 10 solution ideas ranging from 'quick win' to 'moonshot.' For each idea, provide: (1) One-sentence description, (2) How it addresses the user problem, (3) Rough effort estimate (S/M/L), (4) Biggest risk or assumption to validate.

Help me facilitate a sprint retrospective. Here's what happened this sprint: [summary of sprint — what shipped, what didn't, team dynamics, blockers encountered]. Generate: (1) Five 'What went well' observations, (2) Five 'What could be improved' observations, (3) Three 'action items' with specific owners suggested, (4) A discussion prompt that addresses the most impactful improvement area, (5) A format for a 45-minute retro meeting agenda.

I'm presenting to [audience: CEO, board, leadership team] about [topic]. Key message I want to land: [core message]. Supporting data: [metrics and evidence]. Time allotted: [minutes]. Create a slide-by-slide outline with: (1) Recommended title for each slide, (2) Three bullet points of content per slide, (3) One key data point or visual per slide, (4) Speaker notes with anticipated questions. Optimize for a [persuasive/informational/decision-seeking] tone.

Help me triage this bug report: [paste bug details]. Assess: (1) Severity — is this P0 (drop everything), P1 (fix this sprint), P2 (schedule soon), or P3 (backlog)? (2) User impact — who is affected and how broadly? (3) Business impact — revenue, retention, or reputation risk? (4) Recommended immediate action, (5) Root cause hypothesis and what to investigate, (6) A suggested customer communication if we need to acknowledge the issue publicly.