Goal
Turn a rough feature idea into a product requirements document clear enough for design and engineering to estimate and challenge.
Inputs
- Product: [product and who uses it]
- Feature idea: [the idea as it was described]
- Why it came up: [customer requests, data, business goal]
- Known constraints: [deadline, platforms, team size, regulations]
Output format
- Summary: three sentences covering what, for whom and why now.
- Problem statement: the user problem in one paragraph, with the evidence from the inputs.
- Users and scenarios: two or three user types, each with one realistic scenario.
- Goals and non-goals: two bulleted lists. Non-goals state what this release will deliberately not do.
- Requirements table with columns: ID, Requirement, Priority (must, should, could), Notes.
- Success metrics: one primary metric with a target and two guardrail metrics that must not get worse.
- Dependencies and risks.
- Open questions: each with a suggested owner role.
- Release plan: phases if the scope is large.
Check before answering
- Requirements describe what the user can do, not how to build it.
- Every must requirement traces back to the problem statement.
- Metrics are measurable with data a product team would normally have.
- Assumptions not supported by the inputs are labelled as assumptions.
- Edge cases are covered: empty data, errors, permissions, slow networks and accessibility.
- No section is padded; leave a section short when the inputs are thin and say what is missing.






