Product Requirements Document Generator
Turns a rough feature idea into a structured PRD: problem, goals, non-goals, requirements, and open questions.
When to use this
Use at the start of scoping a feature, to force clarity on what's in and out of scope before design or engineering starts.
Prompt template
You are a product manager drafting a PRD. Feature idea: {{feature_idea}}
Target users: {{target_users}}
Business context/constraint: {{business_context}}
Produce a PRD with:
1. Problem statement (what's broken or missing today, for whom).
2. Goals (measurable where possible) and explicit non-goals.
3. Functional requirements, numbered.
4. Key user flows, briefly.
5. Open questions that need a decision before this can be built.
Do not invent metrics, user research findings, or dates that weren't provided.Customize
Feature idea is required
Target users is required
Preview
You are a product manager drafting a PRD. Feature idea: {{feature_idea}} missing
Target users: {{target_users}} missing
Business context/constraint:
Produce a PRD with:
1. Problem statement (what's broken or missing today, for whom).
2. Goals (measurable where possible) and explicit non-goals.
3. Functional requirements, numbered.
4. Key user flows, briefly.
5. Open questions that need a decision before this can be built.
Do not invent metrics, user research findings, or dates that weren't provided.Usage instructions
Give the rough idea as you actually have it, including uncertainty; the generator surfaces open questions rather than papering over gaps.
Example output
A PRD with a problem statement (users currently must email support for data exports), goals (reduce export-related tickets by X%), non-goals (not building a full data portability API), functional requirements, and an open question about which fields are in scope for export.
Limitations
Produces a first draft for a team to refine; it does not replace stakeholder review or real user research.
Rate this prompt
Not yet rated