Product Requirement Prompt Generator
Generates prompts to write a clear, complete product requirement
- Write a PRD for a customer-managed encryption keys (CMEK) feature with per-workspace KMS integration.
- Write a PRD for a native Slack app with slash commands, unfurled links, and DM notifications.
- Write a PRD for a per-workspace data-retention policy admin page with per-object retention windows.
- Write a PRD for a device-management page that lists active sessions and lets a user revoke each remotely.
- Write a PRD for a receipt email that includes a plaintext invoice link and a PDF attachment.
Generated 5 items
See 3 examples
- Example 1
Write a PRD for a customer-managed encryption keys (CMEK) feature with per-workspace KMS integration. Write a PRD for a native Slack app with slash commands, unfurled links, and DM notifications. Write a PRD for a per-workspace data-retention policy admin page with per-object retention windows. Write a PRD for a device-management page that lists active sessions and lets a user revoke each remotely. Write a PRD for a receipt email that includes a plaintext invoice link and a PDF attachment.
- Example 2
Write a PRD for a competitive-battlecard viewer for sales, updated by PMM with usage analytics. Write a PRD for a maintenance-window announcement flow with in-app banners and email 48/24/1 hours before. Write a PRD for a credit-card update reminder before expiration with an in-app card-update flow. Write a PRD for a query-performance dashboard for admins showing slow queries and offending endpoints. Write a PRD for a partner-tier program with certification exams, referral fees, and co-marketing.
- Example 3
Write a PRD for a SOC 2-supporting audit-events pipeline that logs create/read/update/delete for sensitive objects. Write a PRD for an in-app product tour engine that supports branching flows and role targeting. Write a PRD for an in-app changelog widget that surfaces relevant updates to a role, not to all users. Write a PRD for a WhatsApp Business channel integration for two-way customer messaging. Write a PRD for a personal-data map that documents where each PII field is stored, accessed, and retained.
About this generator
The generator draws from 241 practice PRD prompts — each a concrete feature brief such as "Write a PRD for a monthly-usage summary email with breakdown by team and top consumers" — and returns a shuffled selection of however many you request (up to 10). Writing each one forces you to pin down the gaps that commonly sink a feature: unclear scope, missing success metric, or unhandled edge cases. Product managers use this to write a tight spec, run a requirements review, or pressure-test a feature idea before committing engineering time. Answer the relevant questions in writing and the result gives engineering, design, and stakeholders a shared, unambiguous target. The most expensive bugs are the ones written into the spec — a few minutes here saves days of rework.
How to use
- Choose how many prompts you want.
- Generate a set for your feature.
- Answer the relevant ones in writing.
- Share the spec for review before build.
Use Cases
- •Writing a clear product spec
- •Running a requirements review
- •Pressure-testing a feature before build
- •Aligning engineering, design, and stakeholders
- •Avoiding scope and definition gaps
Tips
- →Define scope and what is out of scope.
- →Always set a measurable success metric.
- →Write concrete acceptance criteria.
- →Catch edge cases before engineering does.
FAQ
What kinds of prompts does this generate?
Each prompt is a short feature brief to write a PRD for — onboarding flows, billing emails, admin dashboards, bulk-editing tools, and more. For each, answer the core spec questions: problem definition, scope and out-of-scope, success metrics, acceptance criteria, edge cases, dependencies, and rollout plans.
What makes a product requirement clear enough?
A clear problem statement, a defined scope, a measurable success metric, and concrete acceptance criteria. Ambiguity in any of those four areas is where rework typically originates.
Why answer these questions in writing rather than discussing them?
Writing forces precision and creates a shared artifact. Conversations leave room for each person to walk away with a different understanding; a written spec does not. It also catches gaps when the answer turns out to be 'we don't know yet.'
How detailed should the spec be?
Detailed enough to remove ambiguity, no more. Cover scope, success, edge cases, and the definition of done; skip padding. A tight, answerable spec beats a long, hand-wavy document that nobody references during build.
You might also like
Popular tools from other categories that share themes with this one.