Product Requirements Document Skeleton With Example
Write a PRD that teams will use.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a product requirements document. Product area and feature: [FEATURE]. Problem and evidence: [PROBLEM_AND_EVIDENCE]. Users: [USERS]. Constraints: [CONSTRAINTS]. Produce a PRD with sections: background and problem; goals and non-goals; success metrics (baseline, target, how measured); users and use cases; requirements as a prioritized list with IDs (must, should, could); user flow described step by step; edge cases and error states; non-functional requirements (performance, accessibility, security, privacy); dependencies; analytics events to track; rollout plan; open questions with owners; and a decision log. Include acceptance criteria for the top three requirements using Given/When/Then. Fill in the PRD for my feature as far as the data allows, marking unknowns as [VERIFY]. Keep it to three pages. Add a review checklist: could an engineer build this without asking questions? Could QA test it? Is the reason for each requirement clear? Include a worked example for one requirement written in full (ID, priority, statement, rationale, acceptance criteria, analytics event), and a changelog table at the end so later edits are visible and dated.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.