This PRD prompt is made for product managers, founders, and indie developers: you have just one product idea in mind — say, "a mini-program that helps neighborhood shops keep books and reconcile accounts." Paste the prompt below together with your idea into an AI chat, and it will produce a complete product requirements document in one pass: background, target users, feature list, acceptance criteria, and non-goals. Developers can take it and start scheduling right away, without coming back to ask what each feature is supposed to look like.
A PRD Prompt You Can Copy and Paste
You are a product manager with 8 years of experience, writing a PRD (product requirements document) for the product idea below. The development team will schedule and build directly from this document.
Product idea: [Describe your product in one sentence, e.g.: a mini-program that helps neighborhood shops keep books and reconcile accounts]
Follow this structure and do not skip any section:
1. Background and problem: whose problem this solves, and how they work around it today.
2. Target users: 2-3 user types, one sentence each on their situation and pain points.
3. Product goal: one sentence on what this release delivers, plus 2-3 measurable success criteria.
4. Feature list: three tiers — "Must have / Should have / Could have" — with one sentence of description and one acceptance criterion per feature.
5. Core flow: the steps, no more than 5, a user takes to complete the main task.
6. Non-goals: 3 things explicitly out of scope for this release, so the scope does not creep during development.
7. Open questions: up to 3 pieces of information you need from me — do not invent answers.
Requirements: every feature must have an acceptance criterion; mark anything uncertain instead of making up numbers.Two Small Changes That Make a Big Difference
You only need to replace [Product idea] to use it — but the more specific the idea, the more usable the document. "A bookkeeping mini-program" is weaker than "a mini-program that helps neighborhood shops keep books, reconcile accounts, and export records for their accountant." To make it fit even better, add two more variables under the product idea: [Target platform: mini-program / Web / App] and [First release date: e.g., in 4 weeks] — the AI will cut features by platform and prioritize by timeline.
If the output is too vague, follow up with: "Cut the feature list to 5 items or fewer, and for each one, state what is lost by not building it." If an acceptance criterion is too fuzzy, ask: "Turn 'smooth experience' into a measurable number, for example opening in under 2 seconds." If your idea is still a pile of scattered thoughts, use the requirements-organizing prompt to turn those thoughts into a list first, then come back to write the PRD — don't reverse the order.
Three Limits to Know Before You Use It
This prompt fits a first-version PRD: a simple product with no more than 10 features and no more than 3 user roles. For complex systems — multi-device sync, multi-role permissions, payment compliance — treat the AI's document as a draft and have a human review its structure and boundaries. The AI may also invent numbers: market size, user counts, conversion rates. Any number without a source must be checked or removed before it goes into a document for developers. And don't paste real trade secrets, unannounced product details, or user private data into the chat — strip sensitive information first. Before sending it to developers, run three checks: every feature has an acceptance criterion, the non-goals list has 3 items, and no numbers are invented.
