Product management requires extensive writing—PRDs, sprint planning documents, stakeholder updates, competitive analyses, OKR drafts, and roadmap presentations consume significant PM time. While AI doesn't eliminate this writing burden, it meaningfully accelerates formulaic and tedious sections.
The prompts below are organized by PM task category. They work because they assign specific jobs to AI with sufficient context. More detailed input yields better output. Adapt them to your circumstances.
Key tip: For regular prompt use, store them where retrieval is fast. Promptzy is a native Mac app giving you Cmd+Shift+P access from anywhere to instantly paste saved prompts into ChatGPT, Claude, or Cursor.
PRD and Requirements Prompts
1. PRD first draft from a feature brief
"You're a senior PM at a [company type] company. Write a PRD for [feature name]. The problem: [problem description]. Target users: [users]. Success metrics: [metrics]. Constraints: [constraints]. Include: Overview, Problem Statement, Goals & Non-Goals, User Stories, and Requirements."
2. Sharpening a fuzzy problem statement
"Here's my current problem statement: [paste it]. Ask me 5 clarifying questions about: who's affected, how often, current workarounds, and what a measurable outcome looks like. Then rewrite the problem statement based on strong hypothetical answers."
3. Non-goals section
"I'm building [feature] to achieve [goals]. Write 6–8 specific out-of-scope items for v1 that stakeholders might incorrectly assume are included."
4. Translating vague exec requests
"My exec said: '[vague request]'. List your assumptions, write a one-page brief with a problem statement, ask 3 clarifying questions, and suggest a phased rollout."
5. Feature spec review
"Review this feature spec from a critical engineering perspective: [paste spec]. Identify gaps, unaddressed edge cases, missing dependencies, and likely pushback points."
User Story Prompts
6. User story generator
"Feature: [description]. User persona: [persona]. Write 8 user stories in 'As a / I want / So that' format covering happy paths, 2 edge cases, and 1 negative case with acceptance criteria."
7. Breaking epics into sprint-sized stories
"Epic: [description]. Break this into independently testable stories that fit a 2-week sprint. Flag dependencies and suggest implementation sequence."
8. Acceptance criteria writing
"User story: [paste it]. Write specific, testable acceptance criteria in Given/When/Then format that QA can use without clarification."
Sprint Planning Prompts
9. Sprint goal identification
"Backlog items: [list]. Team: [composition]. Capacity: [hours]. Write a coherent sprint goal, flag scope risks, and identify dependencies."
10. Sprint retrospective summary
"Here are our retro notes: [paste]. Organize into 'keep doing,' 'stop or change,' and 'experiments to try.' Format for team sharing."
11. Capacity planning
"Team: [roles]. Sprint length: [weeks]. Known absences: [list]. Ongoing commitments: [list]. Calculate capacity and produce planning docs."
Stakeholder Communication Prompts
12. Executive update email
"Here are my project notes for this week: [paste notes]. Write a 200-word executive update with status indicator (green/yellow/red), what shipped, upcoming priorities, and blockers needing attention."
13. Delay communication
"Feature: [name]. Original target: [date]. New estimate: [date]. Real reason: [honest reason]. Write a direct email to stakeholders explaining what changed and our mitigation steps."
14. Feature launch announcement
"Feature: [name]. Launch date: [date]. Description: [what it does]. Benefits: [user value]. Affected teams: [list]. Write an internal Slack/email announcement under 300 words."
15. Roadmap communication to sales
"Upcoming features: [list]. Translate each into customer value language a salesperson can use. No technical jargon."
16. Cross-functional kickoff agenda
"Project: [name]. Teams involved: [list]. Time: 60 minutes. Write a time-boxed agenda with pre-read, decisions needed, and post-meeting summary template."
Competitive Analysis Prompts
17. Competitor feature teardown
"Competitor: [name]. Product: [description]. Analyze their positioning, core features, differentiators, pricing, apparent weaknesses, and likely future moves."
18. Win/loss analysis
"Deal: [won/lost]. Customer: [profile]. Decision factors: [what they said]. Write a structured analysis with customer summary, ranked decision factors, our performance, and recommendations."
19. "Where do we actually win" analysis
"Our positioning: [summary]. Deal patterns: [what you've noticed]. Define our ideal customer profile, give 3–5 qualifying signals that predict high win rates, and write sales guidance."
Feature Prioritization Prompts
20. RICE scoring
"Features to score: [list each with brief description]. Estimate Reach, Impact, Confidence, and Effort for each. Calculate RICE scores, rank them, and flag inconsistencies."
21. Now/Next/Later roadmap sort
"Backlog features: [list]. Sort into Now (this quarter), Next (next quarter), Later (future/uncommitted) with reasoning."
22. Scope reduction decisions
"We're [X]% done, blocked by [blocker], and need to cut scope. Features: [list]. Assess core vs. non-core and recommend a v1 vs. v1.1 split."
OKR and Strategy Prompts
23. Team OKRs drafting
"Company goal: [goal]. Team scope: [description]. Draft 2–3 Objectives with 3 measurable Key Results each. Avoid output-focused metrics."
24. OKR retrospective
"Our Q[X] OKRs: [paste]. Actual results: [paste]. Analyze what we achieved, what we missed and why, process improvements, and items to carry forward."
25. 6-month strategy one-pager
"Current state: [summary]. Company priorities: [list]. Key risks: [list]. Resources: [what you have]. Write a concise strategy doc explaining the bet, why now, build sequence, success metrics, and risks."
Roadmap Communication Prompts
26. Roadmap narrative
"Our Q[X] features: [list]. Audience: [execs/customers/sales]. Write a 400–600 word narrative explaining the sequencing as a problem-solving story, not a feature list."
27. Roadmap FAQ
"Here's our roadmap: [paste]. Write an FAQ addressing: why obvious features are missing, why sequenced this way, broken promises, how to accelerate something, and why we can't commit to exact dates."
28. Technical roadmap translation
"Technical roadmap items: [list]. Translate each into plain language for non-technical VPs or customers—explain the user or business impact."
Documentation Prompts
29. Release notes
"Shipped tickets: [list]. Write customer-focused release notes highlighting what users can now do. Skip infrastructure changes. Under 300 words."
30. Help documentation
"Feature: [description]. Write a help article with: one-sentence description, when to use it, step-by-step instructions, and troubleshooting for 3 common issues."
Hiring and Team Prompts
31. Job description
"Level: [senior/staff/etc.]. Product area: [description]. Must-have experience: [list]. Team culture: [describe]. Write a specific JD avoiding generic boilerplate. Highlight the actual first 6-month responsibilities."
32. Interview scorecard
"Skills to assess: [list]. Write a scorecard with 2 questions per skill, rubrics for 1/3/5 answer quality, and behavioral red flags."
Two Prompts to Start With
Start with Prompt #1 (PRD first draft) and Prompt #12 (executive update email)—most PMs use these weekly.
The PRD prompt saves ~45 minutes on average. Heavy editing is expected; the starting point is what matters.
Store frequently-used prompts so you can access them mid-workflow without retyping. On Mac, Promptzy gives you keyboard-shortcut access wherever you're writing.
Final Note
These prompts work best with specific context. The more detail you give about your team, product, and situation, the more useful the output. Generic inputs produce generic results.
Save these prompts to Promptzy — free Mac app, Cmd+Shift+P access from anywhere.
Top comments (0)