The PM prompt library

You are a senior product manager. I'll describe a rough problem below.
Rewrite it as: (1) a one-sentence problem statement, (2) who has it and how often,
(3) the current workaround, (4) what "solved" looks like, (5) three assumptions worth testing first.

Rough problem: <<paste here>>

Create a 30-minute user interview guide about <<topic>>.
Include: a warm-up, 8 open, non-leading questions ordered from broad to specific,
2 follow-up probes each, and a closing question. Avoid questions that hint at a solution.

Here are raw notes from user interviews. Extract the top jobs-to-be-done in the format
"When ___, I want to ___, so I can ___." Cluster similar jobs, rank by how often they appear,
and flag any job that contradicts another.

Notes: <<paste notes>>

Act as a skeptical product lead. For the idea below, list every assumption it depends on.
Sort them into a 2x2 of (impact if wrong) x (confidence today). For the top 3 riskiest,
suggest the cheapest test to de-risk each.

Idea: <<paste idea>>

Write a PRD from the brief below. Sections: Problem, Goals & non-goals, Target users,
Key user stories, Requirements (must/should/could), Success metrics, Open questions, Risks.
Be concise; use bullets. Flag anything I left ambiguous rather than inventing it.

Brief: <<paste brief>>

Review this PRD as a demanding director. Point out: missing edge cases, unmeasurable metrics,
scope that should be cut, and any requirement that is a solution in disguise.
End with the 3 changes that would most improve it.

PRD: <<paste PRD>>

For the user story below, write Gherkin-style acceptance criteria (Given/When/Then)
covering the happy path, 2 edge cases, and 1 error state. Keep each scenario independently testable.

Story: <<paste story>>

Break the spec below into a flat list of engineering tickets. For each: a title, a one-line
description, dependencies, and a rough size (S/M/L). Group them into a sensible delivery order.

Spec: <<paste spec>>

Score each item below on RICE (Reach, Impact 0.25-3, Confidence %, Effort in person-weeks).
Show the table, the RICE score, and the ranked order. Note any item where confidence is so low
it should be a spike instead.

Items: <<paste items>>

We are deciding whether to <<decision>>. Write a one-page trade-off memo: the case for,
the case against, what we'd need to believe for each, and a recommendation with a confidence level.

Organize the backlog below into Now / Next / Later. Group by theme, not feature.
For each item give a one-line rationale tied to a goal. Call out anything that doesn't map to a goal.

Backlog: <<paste backlog>>

Write a weekly product update for stakeholders from the notes below. Structure:
Headline (one line), Shipped, In progress, Blocked/need help, Metrics, Next week.
Keep it skimmable, lead with outcomes not activity.

Notes: <<paste notes>>

Turn the proposal below into an executive one-pager: the ask up top, why now, expected impact,
cost, risks, and the decision you need. No more than one page. Cut jargon.

Proposal: <<paste proposal>>

Help me decline this request without damaging the relationship. Acknowledge the need,
explain the trade-off in terms of their goals, and offer an alternative or a revisit date.
Keep it warm and under 120 words.

Request: <<paste request>>

Write two launch blurbs for the feature below: (1) an internal Slack post for the company,
(2) a customer-facing changelog entry. Match tone to each audience; lead with the user benefit.

Feature: <<paste feature>>