AI Prompts for Product Managers: PRDs & User Stories

Create a comprehensive PRD for the following feature:
Feature name: [name]
Product: [your product name and brief description]
Target user: [who this feature is for]
Problem being solved: [the user problem]
Proposed solution: [high-level approach]
Include these sections:
Executive Summary
Problem Statement (with evidence)
Goals and Success Metrics
User Stories (at least 5)
Functional Requirements
Non-Functional Requirements
UX Considerations
Technical Considerations
Out of Scope
Open Questions
Timeline Considerations

Use standard PRD formatting with headers, bullet points, and clear structure.

Write a compelling problem statement for a PRD:
Feature: [feature name]
Target user: [who]
Current pain: [what they struggle with]
Impact of the pain: [consequences]
Evidence: [data, research, or feedback you have]
The problem statement should:
Be specific and measurable where possible
Include user quotes or data if available
Explain why this matters NOW
Set up the solution without describing it
Be 2-3 paragraphs maximum

Write for an audience of engineers and executives.

Define success metrics for this product feature:
Feature: [name and brief description]
Goal: [what success looks like]
Current baseline: [if known]
Timeline: [when we expect to see results]
For each metric, provide:
Metric name
Definition (exactly how it is measured)
Target value
Why this metric matters
How we will track it
Leading indicators

Include:
2-3 primary metrics (north stars)
3-4 secondary metrics (supporting indicators)
1-2 guardrail metrics (things that should NOT decrease)

Help me prioritize these feature requirements:
Feature: [name]
Requirements list:
[List all your requirements]
Business context:
Primary goal: [main objective]
Timeline constraint: [deadline if any]
Resource constraint: [team size/capacity]
Dependencies: [any blockers]

Create a prioritization matrix using RICE or MoSCoW:
Categorize each requirement
Explain the reasoning
Identify what to cut if timeline is tight
Suggest an MVP scope
Recommend a phased approach if applicable

Write the technical considerations section for a PRD:
Feature: [name and description]
Current system: [relevant technical context]
Known constraints: [any technical limitations]
Integrations needed: [systems this touches]
Include:
Architecture considerations
Data requirements
Security requirements
Performance requirements
Scalability considerations
Technical risks
Questions for engineering

Write as a PM, not an engineer—focus on what matters for product decisions, not implementation details.

Generate user stories for this feature:
Feature: [name and description]
Primary user: [who]
Secondary users: [if any]
Main goal: [what users want to accomplish]
For each story:
Use format: "As a [user], I want [goal], so that [benefit]"
Add acceptance criteria (3-5 per story)
Include edge cases where relevant
Note dependencies on other stories

Generate:
5-7 core user stories
3-4 edge case stories
2-3 error handling stories

Prioritize stories in suggested implementation order.

Write detailed acceptance criteria for this user story:
User story: [paste your user story]
Context: [relevant background]
Edge cases to consider: [any known edge cases]
For each criterion:
Be specific and testable
Use Given/When/Then format where appropriate
Include both happy path and error states
Consider accessibility requirements
Note any UI/UX requirements

Generate 8-12 acceptance criteria that an engineer could implement without additional clarification.

Break down this epic into user stories:
Epic: [name and description]
Goal: [what this epic achieves]
Users affected: [who]
Timeline target: [if any]
Create:
Epic summary (2-3 sentences)
List of user stories (8-15 stories)
Suggested story sequencing
Dependencies between stories
MVP vs. full scope recommendation
Estimated story points per story (rough sizing: S/M/L)

Refine this user story for sprint planning:
Original story: [paste your story]
Context: [relevant information]
Concerns raised: [any issues from grooming]
Improve the story by:
Clarifying ambiguous requirements
Adding missing acceptance criteria
Breaking down if too large (suggest split if needed)
Identifying technical dependencies
Adding edge cases not considered
Estimating complexity (story points suggestion)

Output the refined story ready for sprint planning.

Create a competitive analysis for my product:
My product: [name and description]
Market: [industry/category]
Main competitors: [list 3-5 competitors]
Target audience: [who we serve]
Analyze each competitor:
Product overview
Key features (vs. ours)
Pricing model
Target customer
Strengths
Weaknesses
Market positioning

Then provide:
Feature comparison matrix
Positioning map
Our competitive advantages
Areas where we need to improve
Strategic recommendations

Assess the market opportunity for this product/feature:
Product/Feature: [description]
Target market: [who]
Problem being solved: [user pain]
Current alternatives: [how people solve this now]
Analyze:
Market size estimation (if possible to reason about)
Target segment identification
Willingness to pay factors
Barriers to entry
Timing considerations
Risk factors
Go-to-market considerations

Note: Flag areas where additional research would be needed for accurate assessment.

Develop a detailed user persona for product planning:
Product: [your product]
User type: [the persona you are creating]
Research inputs: [any data, interviews, or insights you have]
Create a persona including:
Name and demographic summary
Role and responsibilities
Goals and motivations
Pain points and frustrations
Current tools and solutions they use
Decision-making factors
Common objections
A typical day/workflow
Quotes that represent their perspective
How our product fits their life

Create a customer interview script for product research:
Research goal: [what you want to learn]
Target interviewee: [who you will interview]
Product area: [what part of the product/problem]
Time available: [interview length]
Include:
Introduction script (setting context)
Warm-up questions (2-3)
Core research questions (8-12)
Follow-up probes for key questions
Wrap-up questions
Questions to avoid (and why)

Questions should:
Be open-ended
Avoid leading the witness
Focus on behavior, not hypotheticals
Uncover needs, not validate solutions

Create a roadmap communication for stakeholders:
Roadmap period: [timeframe]
Audience: [who this is for]
Major initiatives:
[List your planned initiatives]
Create:
Executive summary (2-3 sentences)
Strategic themes for the period
Major deliverables by quarter/month
What we are NOT doing (and why)
Key dependencies and risks
How this connects to company goals
Success criteria for the roadmap

Format for presentation to [leadership/customers/team].

Help me prioritize these product initiatives:
Initiatives:
[List all candidate initiatives]
Context:
Company strategic priorities: [list]
Resource constraints: [team size, timeline]
Current product gaps: [known weaknesses]
Customer feedback themes: [top requests]

Evaluate each initiative on:
Strategic alignment
Customer impact
Revenue potential
Effort required
Risk level
Dependencies

Provide a recommended prioritization with reasoning.

Help me plan the product quarter:
Quarter: [Q1/Q2/Q3/Q4] [Year]
Team capacity: [engineers, designers, etc.]
Carryover from last quarter: [unfinished work]
Strategic priorities: [company goals]
Major commitments: [anything already promised]
Create a quarterly plan including:
Quarter theme/goal
Major initiatives (2-4)
Supporting work
Technical debt allocation
Buffer for unknowns
Key milestones
Risks and mitigations
Success metrics for the quarter

Write a sprint goal for our upcoming sprint:
Sprint number/dates: [info]
Major work items:
[List the key stories/tasks]
Theme: [if there is one]
Dependencies: [blockers or external factors]
The sprint goal should:
Be outcome-focused, not task-focused
Be achievable within the sprint
Be measurable
Align with quarterly objectives
Be understandable to stakeholders

Provide 3 options and recommend the best one.

Write a stakeholder update for my product area:
Update period: [timeframe]
Audience: [executives/team/customers]
Product area: [what you own]
Key updates:
Shipped: [what launched]
Progress: [what is in flight]
Metrics: [relevant numbers]
Blockers: [issues]
Upcoming: [what is next]

Format as a concise update that:
Leads with the most important news
Uses data where available
Is honest about challenges
Ends with clear asks or next steps
Takes 2 minutes to read

Write a feature launch announcement:
Feature: [name and description]
Launch date: [when]
Target audience: [who it is for]
Key benefits: [main value]
How to use it: [brief instructions]
Create:
Internal announcement (for the company)
External announcement (for customers)
One-line summary for social/tweets

Tone: [excited/professional/understated]
Include: Call to action for each version.

Write a brief for engineering on this feature:
Feature: [name]
PM context: [why we are building this]
User need: [the problem]
Proposed solution: [high-level approach]
Success metrics: [how we measure success]
Timeline expectations: [rough dates]
Open questions: [things you need eng input on]
The brief should:
Give engineers enough context to ask good questions
Be clear about what is fixed vs. flexible
Not prescribe implementation details
Highlight technical risks you have identified
Make clear what decisions need eng input

Create a decision document for this product decision:
Decision needed: [what we need to decide]
Options being considered:
[List the options]
Context:
Why this decision matters: [impact]
Who is affected: [stakeholders]
Timeline: [when we need to decide]
Constraints: [limitations]

For each option, analyze:
Description
Pros
Cons
Risks
Resource implications
Reversibility

Include:
Recommendation with reasoning
Implementation next steps if approved

Create a SWOT analysis for my product:
Product: [name and description]
Market context: [industry, competition]
Recent developments: [anything relevant]
Create a detailed SWOT:
Strengths:
What does the product do well?
What advantages do we have?

Weaknesses:
Where does the product fall short?
What do competitors do better?

Opportunities:
Market trends we can capitalize on
Unmet customer needs
Potential expansions

Threats:
Competitive threats
Market changes
Technical risks

For each point, provide specific examples, not generic statements.

Create a cost-benefit analysis for this feature:
Feature: [name and description]
Estimated effort: [if known]
Target outcome: [what we hope to achieve]
Analyze:
Benefits:
User value (with evidence)
Business value (revenue, retention, etc.)
Strategic value
Indirect benefits

Costs:
Development effort
Ongoing maintenance
Opportunity cost (what we cannot build)
Risk costs

Calculate/estimate:
Rough ROI
Payback period
Break-even requirements

Recommendation with confidence level.

Analyze the jobs to be done for this user scenario:
User: [who]
Context: [situation they are in]
Product: [your product]
Feature area: [specific area of focus]
Identify:
Functional jobs:
What is the user trying to accomplish?
What tasks are they performing?

Emotional jobs:
How do they want to feel?
What do they want to avoid feeling?

Social jobs:
How do they want to be perceived?
What relationships/status matters?

For each job:
Current solutions
Gaps/frustrations
Opportunity for our product

Prioritize jobs by importance to the user.

Create a risk assessment for this product initiative:
Initiative: [name and description]
Timeline: [duration]
Stakeholders: [who is involved]
Dependencies: [external factors]
Identify risks in these categories:
Technical risks
Market risks
Resource risks
Timeline risks
Dependency risks
Adoption risks

For each risk:
Description
Likelihood (High/Medium/Low)
Impact (High/Medium/Low)
Mitigation strategy
Owner (role responsible)

Provide overall risk rating and go/no-go recommendation.

Create a launch checklist for this feature:
Feature: [name and description]
Launch date: [target date]
Launch type: [big bang/phased/silent]
Teams involved: [engineering, marketing, support, etc.]
Create checklist by phase:
Pre-launch (1-2 weeks before):
[ ] Technical readiness items
[ ] Documentation items
[ ] Communication items
[ ] Testing items

Launch day:
[ ] Deployment steps
[ ] Monitoring items
[ ] Communication items

Post-launch (first week):
[ ] Monitoring items
[ ] Feedback collection
[ ] Bug response
[ ] Success validation

Include owners and timing for each item.

Design a beta program for this feature:
Feature: [name and description]
Goals: [what you want to learn]
Timeline: [beta duration]
Constraints: [any limitations]
Define:
Beta criteria (who qualifies)
Recruitment strategy
Beta size and composition
Success criteria for the beta
Feedback collection methods
Communication plan with beta users
Escalation process for issues
Graduation criteria to GA

Include template for beta invitation email.

Create a GTM brief for this feature launch:
Feature: [name and description]
Target customer: [who]
Launch date: [when]
Business goal: [what success looks like]
Include:
Feature positioning statement
Key messages (3-5 bullet points)
Target audience segments
Competitive differentiation
Launch timing rationale
Marketing channel recommendations
Sales enablement needs
Customer success preparation
Success metrics
Risks and mitigations

Generate problem validation questions for this hypothesis:
Hypothesis: [your assumption about the problem]
Target user: [who has this problem]
Context: [relevant background]
Create questions to validate:
Does this problem exist?
How severe is the problem?
How do people currently solve it?
How much would they pay to solve it?
Is the timing right?

For each area, provide:
3-4 specific interview questions
What good answers look like
What bad answers look like
Red flags to watch for

Create a solution validation plan:
Solution: [your proposed solution]
Problem it solves: [the user problem]
Target users: [who]
Validation timeline: [how long you have]
Design validation to test:
Usability (can users use it?)
Value (do users want it?)
Feasibility (can we build it?)
Viability (is it sustainable?)

For each:
Specific test/experiment design
Sample size needed
Success criteria
Timeline
Resources required

Include go/no-go decision criteria.

Design an A/B test for this feature:
Feature/Change: [what you are testing]
Hypothesis: [what you believe will happen]
Success metric: [primary metric]
Context: [relevant background]
Define:
Control experience
Variant experience
Primary metric (with significance threshold)
Secondary metrics
Guardrail metrics (should not decrease)
Sample size requirements
Test duration
Segment considerations
Success criteria
What we will do based on results (each scenario)

Create an agenda for this meeting:
Meeting type: [sprint planning/stakeholder review/etc.]
Duration: [time]
Attendees: [who]
Goal: [what the meeting should accomplish]
Context: [relevant background]
Include:
Opening (set context)
Main topics with time allocations
Discussion questions for each topic
Decision points
Wrap-up and next steps

Format for easy sharing. Include pre-work if needed.

I received this feedback on my PRD. Help me address it:
PRD summary: [brief description]
Feedback received:
[Paste the feedback]
For each piece of feedback:
Summarize the concern
Assess if it is valid
Suggest how to address it
Provide revised text if needed

Also identify:
Feedback I should push back on (and why)
Feedback that reveals missing information
Patterns in the feedback to learn from

Write a one-pager for this product initiative:
Initiative: [name]
Goal: [what it achieves]
Timeline: [when]
Team: [who is involved]
The one-pager should include:
Problem statement (2-3 sentences)
Proposed solution (2-3 sentences)
Success metrics (3-4 bullets)
High-level timeline
Resource requirements
Key risks
Ask (what you need from stakeholders)

Total length: One page when formatted.
Audience: [executives/team/stakeholders]

Help me prepare for backlog grooming:
Stories to discuss:
[List the stories]
For each story, help me identify:
Potential clarifying questions from engineering
Hidden complexity
Dependencies not yet called out
Missing acceptance criteria
Suggested story point range
Questions I should ask the team

Also suggest:
Optimal discussion order
Stories that should be split
Stories that can be quick discussions

Write OKRs for my product area:
Product: [your product/area]
Company objectives: [relevant company OKRs]
Quarter: [timeframe]
Team composition: [resources]
Current state: [where you are]
Create:
2-3 Objectives (qualitative, inspiring)
3-4 Key Results per Objective (quantitative, measurable)

For each Key Result:
Specific metric
Current baseline
Target value
Confidence level
How it will be measured

Key Results should be:
Measurable
Ambitious but achievable
Outcomes, not outputs
Within the team's control

Create a post-mortem document for this incident/launch:
What happened: [brief description]
Impact: [who was affected and how]
Timeline: [when it happened]
Resolution: [how it was fixed]
Structure the post-mortem:
Executive summary
Timeline of events
Impact assessment
Root cause analysis
What went well
What went wrong
Action items (with owners and due dates)
Lessons learned
Follow-up meeting schedule

Tone: Blameless, focused on learning and improvement.

Create a product strategy document:
Product: [name]
Time horizon: [1 year/3 years]
Market context: [relevant trends]
Company strategy: [how this fits]
Include:
Vision (where we are going)
Mission (how we get there)
Strategic pillars (3-4 focus areas)
For each pillar: goal, initiatives, metrics
What we will NOT do
Key assumptions
Risks and mitigations
Resource requirements
Success criteria

Write for leadership approval. Include executive summary.

Create a vendor evaluation framework for this need:
Need: [what you are looking for]
Use case: [how it will be used]
Requirements: [must-haves]
Nice to haves: [bonus features]
Budget: [range]
Timeline: [when you need to decide]
Create:
Evaluation criteria with weights
Scoring rubric (1-5 for each criterion)
Comparison matrix template
Key questions to ask each vendor
Reference check questions
Decision framework
Implementation considerations

Create a stakeholder management plan for this initiative:
Initiative: [name and description]
Timeline: [duration]
Impact: [who is affected]
Identify stakeholders by category:
Decision makers
Influencers
Implementers
Users/beneficiaries

For each key stakeholder:
Name/role
Interest level (high/medium/low)
Influence level (high/medium/low)
Concerns/interests
Communication approach
Frequency of updates

Include a RACI matrix for key decisions.