Product managers are professional writers, though they rarely see themselves that way. PRDs, user stories, acceptance criteria, roadmap narratives, release notes, stakeholder updates, meeting summaries, and strategy documents add up to hours of writing every week that compete with the thinking and decision-making the role actually demands, we have create a list of chatGPT prompts for product manager to make their lives easier.
These prompts cover the core PM writing workflow. Use them to generate clear first drafts fast so you can spend your time improving the thinking, not staring at a blank page.
Product Requirements Prompts
Product requirements document (PRD)
Write a product requirements document for [feature or product name]. Background and context: [why we are building this]. Problem being solved: [describe the user or business problem]. Target users: [who this is for]. Goals and success metrics: [what success looks like, with specific metrics]. Scope: [what is in and out of scope]. Requirements: [list functional requirements]. Open questions: [list anything not yet decided]. Use standard PRD structure with clear headings. I will refine the requirements section after seeing the draft.
User stories
Write user stories for [feature name] from the perspective of [user type]. For each story use the format: As a [user type], I want to [action], so that [benefit]. Write 8 user stories covering the main use cases for this feature: [describe the feature briefly]. For each story, add 3 acceptance criteria in Given/When/Then format that define when the story is complete.
Feature brief
Write a one-page feature brief for [feature name] to share with the engineering and design team. Include: the problem this feature solves, who it is for, why we are prioritising it now, what it needs to do at a high level (not detailed specs), what success looks like, and what we are explicitly not building in this version. Keep it concise and opinionated. Under 300 words.
Acceptance criteria writer
Write acceptance criteria for the following user story: [paste user story]. Write 5 to 8 acceptance criteria in Given/When/Then format that cover: the happy path, edge cases, error states, and any performance or accessibility requirements relevant to this story. Be specific enough that a developer knows exactly what to build and a QA engineer knows exactly what to test.
Roadmap and Strategy Prompts
Roadmap narrative for stakeholders
Write a roadmap narrative for [product or team] covering [Q1 / H1 / the next 6 months]. Themes and priorities: [list the 3 to 4 themes with brief descriptions]. What we are not doing and why: [list any deliberate exclusions]. Key assumptions: [what needs to be true for this roadmap to hold]. Write for a non-technical audience of senior stakeholders. The narrative should explain the thinking, not just list the items. Under 400 words.
Product strategy one-pager
Write a product strategy one-pager for [product name]. Include: the market opportunity, our target customer and their core problem, our approach and differentiation, the 3 strategic bets we are making, how we will measure success, and what we need to be true for the strategy to work. Under 400 words. Written for a leadership audience that will challenge assumptions.
Prioritisation rationale
Write a prioritisation rationale explaining why we are building [feature A] before [feature B] in [Q/period]. Arguments for [feature A]: [list]. Arguments that might favour [feature B]: [list]. Our reasoning for the decision: [explain]. What would change the prioritisation: [list conditions]. Under 200 words. Clear and defensible without being bureaucratic.
Stakeholder Communication Prompts
Weekly product update
Write a weekly product update for [audience: engineering team / leadership / company all-hands]. This week: [what shipped, what is in progress, what is blocked]. Next week: [priorities]. Key decisions made: [list]. Open questions needing input: [list]. Format as a short structured update under 200 words. Factual and direct, not padded with status theatre.
Delay or scope change communication
Write a stakeholder communication about a [delay / scope change] to [feature or project name]. Original timeline or scope: [X]. New timeline or scope: [X]. Reason for the change: [explain honestly]. Impact on other teams or commitments: [describe]. What we are doing to minimise the impact: [explain]. Under 200 words. Direct and honest without over-apologising.
Executive product review prep
Help me prepare for an executive product review for [product or feature]. Key metrics to present: [list with current numbers]. What is going well: [list]. What is not going well and why: [honest assessment]. Decisions I need from the exec team: [list]. Questions I expect to face and my planned answers: [list 3 to 5 likely questions]. Format as a structured prep document I can review before the meeting.
Release and Launch Prompts
Release notes
Write release notes for version [X.X] of [product name]. Features shipped: [list with brief descriptions]. Bug fixes: [list]. Known issues: [list if any]. Write two versions: one for technical users (include detail, call out API changes or breaking changes if any) and one for end users (plain English, focus on what they can now do, not how it works). Each under 200 words.
Internal launch announcement
Write an internal launch announcement for [feature or product name] going live on [date]. Include: what we built and why, who it is for, what it does in plain terms, how to access or use it, who to contact with questions, and a brief acknowledgment of the team who built it. Under 200 words. Energetic and clear.
Go-to-market brief for a feature launch
Write a go-to-market brief for the launch of [feature name]. Target audience: [who will use this]. Key message: [what we want them to understand]. Launch channels: [email / in-app / blog / social / sales enablement]. Key dates: [list milestones]. Success metrics for the launch: [what does a good launch look like]. What each team needs to do: [list by function: marketing, sales, support, engineering]. Under 400 words.
Discovery and Research Prompts
User interview question guide
Write a user interview question guide for [research goal: understanding how users currently solve X / evaluating interest in a new feature / identifying pain points in the current product]. Include: 2 warm-up questions, 5 to 7 core discovery questions, 2 questions about existing solutions or workarounds, and 1 closing question. Avoid leading questions. Format as a guide with notes on what to listen for after each question.
Research synthesis summary
Summarise the following user research notes into a clear synthesis: [paste interview notes or research findings]. The summary should cover: the top 3 to 5 themes that emerged, specific quotes or evidence supporting each theme, what the findings suggest about user needs or pain points, and the key implications for the product. Under 300 words. Evidence-based and actionable.
For prompts covering the strategy and business side of product work, see our ChatGPT prompts for business guide. For prompts that help with stakeholder communication and writing, see our ChatGPT for email writing guide. For the techniques that produce better output from complex prompts, see our prompt engineering techniques guide.






Leave a Reply