The 35 Best AI Prompts for Product Managers
Product management involves an absurd amount of writing. PRDs, sprint planning docs, stakeholder updates, competitive analyses, OKR drafts, roadmap decks — most PMs I know spend more time writing about work than actually doing it. AI doesn't eliminate that writing, but it meaningfully speeds up the parts that are formulaic and painful.
The prompts below are organized by PM task. They're not "magic prompts" — they work because they give the AI a specific job with enough context to do it well. The more context you provide, the better the output. Copy them, adapt the brackets, and make them yours.
One practical note: if you use prompts regularly, save them somewhere you can retrieve them fast. I built Promptzy for this — it's a native Mac app that lets you Cmd+Shift+P from anywhere and paste any saved prompt directly into ChatGPT, Claude, or Cursor in under 2 seconds. The retrieval friction is the thing that kills prompt reuse.
PRD and Requirements Prompts
1. PRD first draft from a feature brief
I'm a product manager at [COMPANY TYPE — B2B SaaS, consumer app, etc.]. I need to write a PRD for a feature: [FEATURE NAME].
Here's what I know:
- Problem we're solving: [DESCRIPTION]
- Who it's for: [USER PERSONA]
- What success looks like: [METRIC OR OUTCOME]
- Constraints: [TECHNICAL / TIMELINE / SCOPE]
Write a PRD with these sections: Overview, Problem Statement, Goals & Non-Goals, User Stories, Requirements (functional and non-functional), Open Questions. Keep it concise — we don't write 20-page PRDs. Flag anything where you need more info from me.
2. Sharpening a fuzzy problem statement
Here's my current problem statement for a feature:
"[PASTE YOUR PROBLEM STATEMENT]"
This feels vague. Help me sharpen it. Ask me 5 questions that would help us write a more specific problem statement — who exactly is affected, how often, what's the workaround they use today, and what measurable outcome we're trying to move. Then rewrite the problem statement based on hypothetical strong answers.
3. Non-goals section (the part everyone skips)
I'm building [FEATURE]. The goals are: [LIST GOALS].
Help me write a non-goals section. What are the things that will be out of scope for v1 that stakeholders might assume are in scope? Be specific — generic non-goals like "this won't handle all edge cases" aren't useful. Give me 6-8 specific non-goals that would actually prevent scope creep on this feature.
4. Translating a vague exec request into a requirements doc
An exec just asked for this: "[PASTE THE VAGUE REQUEST]"
Help me translate this into a structured requirements doc. First, list the assumptions I'm making to fill in the gaps. Then write a one-page brief with: the problem we're solving, what "done" looks like, 3 questions I should clarify with the exec before starting, and a suggested phased rollout (v1 → v2) if appropriate.
5. Feature spec review
Here's a feature spec I wrote:
[PASTE SPEC]
Review it as a skeptical senior engineer who will have to build this. Where are the gaps? What edge cases haven't I thought through? What dependencies am I missing? What would a good engineer push back on in the kickoff meeting?
User Story Prompts
6. User story generator from a feature description
Feature: [DESCRIPTION]
User persona: [PERSONA NAME AND KEY CHARACTERISTICS]
Write 8 user stories in the format: "As a [type of user], I want to [goal], so that [outcome]." Include: the happy path, 2 edge cases, and 1 negative case (what the user does NOT want). Add acceptance criteria for each story.
7. Breaking an epic into sprint-sized stories
Here's an epic: [EPIC DESCRIPTION]
Break this into user stories small enough to complete in a single sprint (assuming a 2-week sprint, team of 4). Each story should be independently testable and deliverable. Flag any dependencies between stories. Order them by recommended implementation sequence.
8. Acceptance criteria for a specific story
User story: "[PASTE STORY]"
Write specific, testable acceptance criteria. Format each as "Given [context], when [action], then [expected result]." Include edge cases. A QA engineer should be able to write automated tests from these criteria without asking me questions.
Sprint Planning Prompts
9. Sprint goal from a backlog of tickets
Here are the tickets we're considering for our next sprint:
[LIST TICKETS/EPICS]
We're a team of [N] engineers + [N] designers with [N] capacity days. Help me: 1) identify a coherent sprint goal that ties these together, 2) flag any tickets that don't fit the goal and should move out, 3) identify dependencies I need to resolve before sprint start.
10. Sprint retrospective summary
Here are notes from our sprint retrospective:
[PASTE NOTES]
Summarize the key themes. Group feedback into: what's working (keep doing), what's not working (stop or change), and experiments to try next sprint. Write it as a short Confluence/Notion-style doc I can share with the team and stakeholders.
11. Capacity planning doc
Our team has: [N] engineers, [N] designers, [N] PMs. Sprint length: [N] weeks. Known absences: [NAMES AND DATES]. Ongoing commitments (bug fixes, on-call, etc.): [ESTIMATE].
Calculate actual available capacity in story points or days. Then help me write a capacity planning section for our sprint planning doc, including a risk note if we're near the edge of what's realistic.
Stakeholder Communication Prompts
12. Executive update email (concise)
I need to write a weekly update to our VP/C-suite about [PROJECT/TEAM]. Here's what happened this week:
[BULLET POINT NOTES]
Write a 200-word update formatted as: 1-sentence status (green/yellow/red), what we shipped, what's coming next week, and any blockers that need exec attention. Skip the filler. Execs don't need context they already have.
13. Delay communication
We're going to miss our deadline for [FEATURE/PROJECT]. Original target was [DATE]. New estimate is [DATE]. The reason is [HONEST EXPLANATION].
Write an email to [STAKEHOLDERS] communicating this. Requirements: don't make excuses, be specific about what changed, explain what we're doing differently to hit the new date, and tell them what they need to do (if anything). Tone: direct and confident, not apologetic or defensive.
14. Feature launch announcement (internal)
We're launching [FEATURE] on [DATE]. It does [DESCRIPTION]. The main user benefit is [BENEFIT]. It affects [WHO IN THE ORG — support, sales, etc.].
Write an internal launch announcement for Slack/email. Include: what it is in one sentence, why we built it, how it works in 2-3 sentences, what support/sales needs to know, and a link to the full doc. Keep it under 300 words.
15. Roadmap communication to sales
I need to update our sales team on the product roadmap. Here's what's coming in the next quarter:
[LIST FEATURES/THEMES]
Write a sales-friendly summary that focuses on customer value, not technical details. For each item, frame it as: "This helps customers who [PROBLEM] because [SOLUTION/OUTCOME]." End with guidance on what they can and can't commit to in customer conversations.
16. Cross-functional kickoff agenda
I'm running a kickoff meeting for [PROJECT] with [TEAMS — eng, design, data, marketing]. Duration: 60 minutes. Goal: align on scope, timeline, and responsibilities.
Write an agenda with: pre-read to send 48 hours before, time-boxed sections for the meeting, and a list of decisions that must be made vs. topics to table for later. Also write a post-meeting summary template I can fill in right after.
Competitive Analysis Prompts
17. Competitor feature teardown
I'm analyzing [COMPETITOR PRODUCT] for a competitive review. Here's what I know about them:
[PASTE WHAT YOU KNOW — website copy, pricing page, feature list, reviews]
Help me structure a competitive teardown. Cover: positioning (who they're targeting), core features and differentiators, pricing model, apparent weaknesses based on public reviews, and what they're likely building next. Flag where my data is thin and I should do more research.
18. Win/loss analysis template
I just had a deal close [FOR / AGAINST] us. Customer profile: [DESCRIPTION]. They chose [US / COMPETITOR]. The reasons given were: [REASONS].
Help me write a structured win/loss analysis note. Include: customer profile summary, decision factors ranked by importance, what we did/didn't do well, competitive positioning, and 1-2 product/sales recommendations from this case.
19. "Where do we actually win" analysis
Here's our positioning vs. [COMPETITOR]:
- Our strengths: [LIST]
- Their strengths: [LIST]
- Common objections we lose on: [LIST]
- Deals we tend to win: [DESCRIPTION]
Based on this, help me define the specific customer profile where we win reliably. What are the 3-5 qualifying signals that predict a high win rate? Write a "when to compete" guide for our sales team.
Feature Prioritization Prompts
20. RICE scoring for a backlog
I need to prioritize these features using RICE (Reach, Impact, Confidence, Effort):
[LIST FEATURES]
For each, help me estimate: Reach (how many users per quarter), Impact (1-3 scale), Confidence (percentage), Effort (person-months). Then calculate RICE scores and rank them. Flag where my estimates seem inconsistent with each other.
21. Now/Next/Later roadmap sort
Here's our backlog of features:
[LIST]
Sort these into: Now (shipping this quarter), Next (next quarter), Later (in the future / not committed). Use these criteria:
- Now: highest user impact, aligns with current company priority, team has capacity
- Next: important but has a dependency or needs more discovery
- Later: good idea, no commitment yet
Show your reasoning for each placement. Push back if anything looks like a "maybe" masquerading as "now."
22. Deciding what to cut from scope
We're [N] weeks into a [N]-week project. We've hit a blocker: [DESCRIPTION]. To hit the original launch date, we need to cut scope.
Here's what's currently in scope:
[LIST FEATURES/REQUIREMENTS]
Help me identify what to cut vs. what's core. For each item, assess: would cutting this break the core use case? Would users notice immediately? Could we add it back in a v1.1? Suggest a v1 vs. v1.1 split.
OKR and Strategy Prompts
23. Drafting team OKRs
Our company's Q[N] goal is: [COMPANY OKR].
My team is responsible for: [TEAM SCOPE].
Help me draft 2-3 team Objectives with 3 Key Results each. Requirements: KRs must be measurable (not "improve X" but "increase X from Y to Z by [DATE]"). OKRs should ladder to the company goal without just restating it. Flag any KR that's an output rather than an outcome.
24. OKR retrospective
Here were our Q[N] OKRs:
[PASTE OKRs]
Here are our actual results:
[PASTE RESULTS]
Write a retrospective that covers: what we hit and why, what we missed and the real reason (not the PR version), what we'd change in how we set or measured these, and what carries forward to next quarter.
25. 6-month strategy one-pager
I need to write a 6-month strategy document for [TEAM/PRODUCT AREA]. Here's the context:
- Current state: [DESCRIPTION]
- Company priorities: [DESCRIPTION]
- Key risks: [DESCRIPTION]
- Resources: [TEAM SIZE / BUDGET]
Write a one-page strategy doc with: the bet we're making, why now, what we're building and in what order, how we'll know if it's working, and what could go wrong. Keep it short enough that an exec can read it in 3 minutes.
Roadmap Communication Prompts
26. Roadmap narrative (not just a timeline)
Here's our roadmap for [TIMEFRAME]:
[LIST THEMES OR FEATURES BY QUARTER]
Write a narrative version of this roadmap that explains the "why" behind the sequencing. Not a feature list — a story of how we're going to solve [CUSTOMER PROBLEM] by [TIMEFRAME]. Audience: [INTERNAL STAKEHOLDERS / CUSTOMERS / INVESTORS]. Length: 400-600 words.
27. Roadmap FAQ (pre-empting stakeholder questions)
Here's our upcoming roadmap:
[PASTE ROADMAP]
Write a FAQ for the questions I'll definitely get asked:
- Why isn't [OBVIOUS THING] on the roadmap?
- Why is [X] before [Y]?
- What happened to [THING WE PROMISED]?
- Can we move [X] up?
- When exactly is [X] launching?
Answer each one honestly, the way I'd want to answer it — not a PR non-answer.
28. Translating a technical roadmap for a non-technical audience
Here's our technical roadmap:
[PASTE TECHNICAL ITEMS]
Translate each item into plain language that a VP of Sales or a customer could understand. Format: one sentence per item explaining what changes for users or the business. No jargon, no architecture terms.
Documentation Prompts
29. Release notes from a ticket list
Here's the list of tickets/features we shipped in [RELEASE VERSION]:
[LIST TICKETS]
Write release notes formatted for [CUSTOMERS / INTERNAL TEAM]. For customer-facing: focus on what they can do now that they couldn't before, written from the user's perspective. Skip internal infrastructure changes. Keep it under 300 words.
30. Help doc for a new feature
I need to write a help article for [FEATURE]. Here's how it works:
[TECHNICAL DESCRIPTION]
Write a help doc for a user who's never seen this feature. Structure: what it is (one sentence), when to use it, step-by-step instructions with clear action verbs, and a troubleshooting section for the 3 most likely things that go wrong. Avoid jargon.
Hiring and Team Prompts
31. Job description for a PM role
I'm hiring a [SENIOR / MID / ASSOCIATE] PM for [PRODUCT AREA]. Here's what they'll work on: [DESCRIPTION]. Must-have experience: [LIST]. Nice-to-have: [LIST]. Our team culture: [DESCRIPTION].
Write a job description that attracts strong candidates without being generic. Specifically: avoid corporate boilerplate like "you're a self-starter who thrives in a fast-paced environment." Be specific about what they'll actually do in the first 6 months.
32. Structured interview scorecard
I'm interviewing candidates for a PM role. The key skills I'm assessing: [LIST — e.g., prioritization, communication, cross-functional influence, data analysis].
Write a structured scorecard with: 2 questions per skill, a rubric describing what a 1/3/5 answer looks like, and red flags to watch for. The questions should reveal how they actually work, not how they describe working.
Two Prompts Worth Saving First
If you're only going to start with two prompts from this list, make them #1 (PRD first draft) and #12 (executive update email). They come up every week.
The PRD prompt alone saves me 45 minutes on average — not because the AI writes the PRD for me, but because having a structured first draft to react to is faster than building from scratch. I edit the output heavily. That's expected. The starting point is what matters.
If you use any of these regularly, store them where you can access them mid-workflow. Retyping a 200-word prompt from memory every time defeats the purpose. If you're on a Mac, Promptzy keeps them a keyboard shortcut away from wherever you're writing — Cmd+Shift+P, search "PRD", paste. Free to try.
These prompts work best when you add your own context — the more specific you are about your team, product, and situation, the more useful the output. Generic input gets generic output.
Store and manage your prompts with Promptzy
Free prompt manager for Mac. Search with Cmd+Shift+P, auto-paste into any AI app.
Download Free for macOS