Best AI Prompts for Product Managers
These AI prompts for product managers cover the work from the first customer interview to the post-launch review: discovery, strategy, prioritization, specs, experiments and launches. Most ask for your own evidence first, such as interview notes, backlog estimates, baselines or results, so the plan, PRD or readout fits your product instead of reading like a template. The new prompts tell the AI to use only what you give it, mark its assumptions and show the math where there is some. Check the result with your team anyway.
The collection has six groups. Discovery prompts plan customer interviews and usability tests, synthesize notes, map jobs to be done, size an opportunity and analyze customer segments. Strategy prompts draft a one-page strategy, team OKRs, a North Star metric and a competitive teardown. Roadmap prompts score a backlog with RICE, triage feature requests, build a now, next and later roadmap and help you say no. Delivery prompts write a PRD, user stories, a feature spec, an edge case review and a rollout plan. Experiment prompts plan an A/B test, write up the result and investigate a metric that moved. The last group plans a launch, writes release notes and a launch email, sends stakeholder updates and runs the post-launch review.
Most prompts work in ChatGPT, Claude and Gemini. Fill in the blanks, paste it in and edit the result. AI can help you prepare and make sense of research, but it can't talk to your customers for you, so the discovery prompts start from real conversations and data. Keep confidential roadmaps and customer details out unless your company's AI policy allows them. Save your favorites to your Musebox library and remix them.
Discovery and research
Customer Interview Guide — Questions About Past Behavior, Not Opinions
Plan a customer discovery interview: who to talk to, how to open, questions about what people actually did, follow-ups, and a note template, with consent built in.
You're a product discovery coach who has trained dozens of product teams to run interviews that uncover real problems in...
Interview Synthesis — From Raw Notes to Themes and Opportunities
Turn customer interview notes into themes, supporting quotes, opportunities to explore and open questions, with every finding traced back to the evidence.
You're a senior user researcher who synthesizes interviews without inventing patterns that aren't there. Synthesize my n...
Jobs to Be Done Map — What Customers Are Really Trying to Get Done
Map the jobs your customers hire a product for: the main job, the steps, the outcomes they measure, what they use today, and where your product can help most.
You're a product strategist who uses Jobs to Be Done to find where customers struggle. Build a job map from what I know....
Usability Test Plan — Tasks, Script and What to Watch For
Plan a usability test for a prototype or live feature: goals, participants, realistic tasks, a moderator script, what to observe and how to report the findings.
You're a UX researcher who runs lean usability tests that product teams actually act on. Plan my test. What I'm testing...
Opportunity Brief — Is This Problem Worth Solving
Write a short opportunity brief before committing to build: the problem, who has it, evidence, size, why now, risks and the smallest way to learn more.
You're a product leader who asks for a one-page opportunity brief before any team starts building. Write mine. The prob...
Customer Segment Analysis — Quick Prioritization
Segment customers by key dimensions, rank by value, and get targeting recommendations for top segments. Fast audience intelligence for campaign planning.
You're a marketing data analyst. Perform a customer segment analysis. Population: {{customer_population}} Date range: {...
Strategy and goals
Product Strategy One-Pager — Vision, Bets and Trade-Offs
Draft a one-page product strategy: the vision, target customers, the problems you'll solve, your key bets, what you won't do, and how you'll measure progress.
You're a head of product who believes a strategy that fits on one page is a strategy people follow. Draft mine. The pro...
Team OKRs — Outcomes, Not a List of Features
Write objectives and key results for a product team that measure changes in customer behavior and business results, not features shipped, and tie them to company goals.
You're an OKR coach who has helped product teams stop writing roadmaps and calling them key results. Draft my team's OKR...
North Star Metric — One Number and the Inputs That Move It
Choose a North Star metric that reflects the value customers get, with the input metrics your teams can move and the counter-metrics that keep it honest.
You're a product growth lead who has seen teams chase vanity metrics. Help me pick a North Star metric. The product, it...
Competitive Product Teardown — Where We Win and Where We Don't
Compare your product with competitors and alternatives on the jobs customers care about, find real gaps and strengths, and decide what to do about them.
You're a product strategist who does competitive analysis from the customer's point of view, not a feature checklist. Bu...
Prioritization and roadmap
RICE Prioritization — Score the Backlog and Show the Math
Score backlog items with RICE (reach, impact, confidence, effort) from your own estimates, rank them, and flag the scores that rest on weak evidence.
You're a product operations lead who uses scoring to start a better conversation, not to end it. Score my backlog with R...
Feature Request Triage — Themes, Not a Pile of Asks
Sort a pile of feature requests from customers, sales and support into problem themes, count the evidence behind each, and decide what to explore, park or decline.
You're a product manager who turns a messy request backlog into a clear picture of customer problems. Triage my requests...
Outcome Roadmap — Now, Next, Later Without Fake Dates
Turn a list of planned features into an outcome-based roadmap with now, next and later columns, the problem each item solves and how you'll know it worked.
You're a product leader who replaced date-driven feature roadmaps with outcome roadmaps that stakeholders trust. Rework ...
Saying No to a Feature Request — Clear, Kind and Final
Write a clear, respectful reply declining a feature request from a customer, executive or colleague, with the reason, what you'll do instead and what would change your mind.
You're a product manager known for saying no in a way that keeps relationships strong. Help me decline this request. Th...
Specs and delivery
PRD One-Pager — The Problem, the Bet and How We'll Know
Write a short product requirements document: problem, goals and non-goals, users, key requirements, success metrics, risks and open questions, ready for review.
You're a senior product manager who writes PRDs engineers and designers actually read. Write a PRD from my notes. The p...
User Stories — With Acceptance Criteria Engineers Can Test
Break a larger feature into small, independent user stories in build order, with testable acceptance criteria, a first thin slice and splitting suggestions.
You're a product owner who writes stories that engineers can estimate and testers can check. Write stories for this feat...
Feature Spec — From Idea to Buildable Ticket
Turn a feature idea into a spec a developer can build from: the problem, user stories, acceptance criteria, edge cases, data and API changes, and the open questions to settle first.
You're a staff engineer who has seen too many features built from a one-line ticket. Turn my feature idea into a spec a ...
Edge Case Review — What Breaks Before Users Find It
Review a feature or spec for edge cases, error states, permissions, data limits, abuse and accessibility gaps before it's built, with what the product should do in each case.
You're a product manager with a QA lead's instincts, known for finding the cases everyone else missed. Review my spec fo...
Release Plan — Rollout, Feature Flags and Rollback
Plan how a feature reaches users safely: rollout stages, feature flags, who sees it first, the metrics to watch, when to pause and how to roll back.
You're a product manager who has shipped risky changes to millions of users without drama. Plan my rollout. The feature...
Experiments and metrics
A/B Test Plan — Hypothesis, Sample Size and Stop Rules
Plan an A/B test before you run it: the hypothesis, primary and guardrail metrics, a sample size estimate from your baseline and traffic, duration and the rules for calling it.
You're a product experimentation lead who stops teams from peeking at results and calling winners too early. Plan my A/B...
Experiment Readout — What We Learned and What We'll Do
Write up an experiment's results honestly: what you tested, the numbers, whether the result is trustworthy, what you learned and the decision, including when the answer is no difference.
You're a data-minded product manager whose experiment readouts are trusted because they report flat and negative results...
Metric Drop Investigation — Find Out Why a Number Moved
Work through a sudden change in a product metric step by step: check the data first, segment the change, list causes, and plan what to check next.
You're a product analytics lead who has investigated hundreds of "why did this number drop" questions without panicking....
Launch and stakeholders
Launch Plan — Everything That Has to Happen Before Launch Day
Plan a product or feature launch across product, engineering, marketing, sales, support and legal, with owners, dates, a launch day runbook and success measures.
You're a product manager who has run launches where nothing important was forgotten. Build my launch plan. What we're l...
Release Notes — What Changed, Written for Users
Turn a list of changes, tickets or a changelog into release notes users will read: what's new, what improved, what was fixed, and anything they need to do.
You're a product writer who turns engineering changelogs into release notes customers actually find useful. Write my rel...
Product Launch Email — Quick Builder
Write a conversion-focused product launch email with subject line, preview text, and 200-300 word body. Follows hook > problem > solution > proof > CTA structure with clear tone guardrails.
You're a product launch email copywriter. Write copy that's confident and specific — like a smart friend sharing somethi...
Stakeholder Update — Weekly Status Without the Spin
Write a weekly product update for stakeholders: progress against goals, what shipped, risks with owners, decisions needed and what's next, in a format busy people read.
You're a product manager whose weekly updates are the ones leaders actually read, because they're short and honest. Writ...
Post-Launch Review — What Happened Against What We Expected
Review a launch a few weeks later: results against the goals you set, what customers did and said, what went well or badly, and the decisions and follow-ups that come out of it.
You're a product leader who runs post-launch reviews that change how the team works, without blaming anyone. Run mine. ...
Related collections
Best AI Prompts for Marketers
These AI prompts cover the marketing work that eats your week: planning content, writing emails and ads, doing SEO and figuring out who you're selling to. Each one asks for your product, audience and goal up front, so the output is specific enough to publish or present after a light edit. The collection is organized into four groups. Content and social prompts plan a week of posts or a 30-day calendar and turn one blog post into a set of social posts. Email, ad and landing page prompts write welcome sequences, cart recovery flows, launch and win-back emails, search and social ads, and landing page copy. SEO prompts handle blog outlines, content briefs, title tags and meta descriptions, product descriptions, internal links, alt text, schema markup and keyword ideas. Strategy and analytics prompts build customer personas, audience segments, brand voice guides, competitor messaging teardowns, demand tests and campaign reports. Every prompt works with ChatGPT, Claude and Gemini. Copy one, fill in your details and paste it into the assistant you use. Save the ones you rely on to your Musebox library and remix them to fit your brand.
Best AI Prompts for Small Business Owners
These AI prompts for small business owners cover the jobs that land on the owner's desk: planning, pricing, getting paid, finding customers, looking after them, running the place and hiring help. Most of them ask for your real numbers and your own words first, so the plan, quote or email fits your business instead of reading like a template. The new prompts tell the AI to use only what you give it, show its math and mark its guesses. Check the result anyway. The collection has six groups. Planning prompts test an idea before you spend on it, stress-test a plan, map your business model, write a one-page plan and compare you with the competition. Money prompts set prices, write quotes, chase late invoices, forecast cash for 13 weeks and explain your monthly numbers. Marketing prompts improve your Google Business Profile, answer reviews, write a customer newsletter, plan a promotion and plan social posts. Customer prompts handle complaints, write store policies and build a feedback survey. Operations prompts plan your week, plan a project, find the work that matters most, write procedures, compare suppliers and check an agreement before you sign. The last group helps you decide on a first hire, onboard them and brief a contractor. Most prompts work in ChatGPT, Claude and Gemini. Fill in the blanks, paste it in and edit the result. For tax, legal and employment questions, use the output to prepare, then check with a professional where you're based. Save your favorites to your Musebox library and remix them.
Best AI Prompts for Developers
These AI prompts for developers cover the work around the code as well as the code itself: planning a feature, designing the schema, tracking down a bug, reviewing a pull request and writing it all down. Each one asks for your stack, your code and your constraints first, so the answer fits your project instead of a generic tutorial. Most of them list what they assumed and mark gaps instead of inventing APIs, file paths or test results. The collection has seven groups. Planning prompts turn ideas into specs, review system designs, design schemas and APIs, and record architecture decisions. Coding prompts write code from a spec, build accessible React components, write SQL queries and regular expressions, and include a patient mentor for beginners. Reading and refactoring prompts explain unfamiliar code, port it to a new language or framework and plan safe refactors. Debugging prompts find root causes, explain error messages and track down slow code. Testing and review prompts write unit tests, review code and accessibility, and check your own code for security holes. Agent prompts brief Claude Code, Cursor and other coding agents, set up a rules file for your repo and check what the agent wrote. Shipping prompts write READMEs, commit messages, CI pipelines and postmortems. Most prompts work in ChatGPT, Claude and Gemini, and the rest are written for a coding agent that can read your repo. Fill in the blanks, paste it in and check the result before you ship it. Save your favorites to your Musebox library and remix them.