Product Requirements Document From Notes
Turn rough notes into a structured PRD.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Create a product requirements document. Feature or product idea and notes: [NOTES]. Users and problem: [USERS_PROBLEM]. Constraints (technical, legal, timeline): [CONSTRAINTS]. Produce a PRD with: background and problem, goals and non-goals, users and use cases, requirements grouped by priority (must, should, could) each with an ID and acceptance criteria, user flows described in steps, success metrics with targets set as placeholders, dependencies, risks, open questions, and a release approach. Mark anything you inferred as [ASSUMPTION] and list open questions for me to answer. Keep language testable and free of implementation detail unless I specified it. Add a reviewer checklist for the document with ten items covering clarity, testability and completeness, and a table of the open questions with the owner and the date needed. Provide a short executive summary of 100 words at the top of the PRD, and a version history table so that changes are traceable. Add a worked example of three requirements written in the format you will use for the whole document: an ID, a priority, the requirement stated in testable language, acceptance criteria in given-when-then form, and the source note it came from. Use an invented feature such as scheduled report emails. Label it an illustration. Add a traceability table that links each goal to the requirements that serve it, so reviewers can see goals with no requirements and requirements with no goal. Provide a section on scope boundaries listing what is deliberately excluded and why, a list of the ten questions most likely to be asked in review, and a rule that any [ASSUMPTION] must be resolved or accepted by a named person before development starts. Close with a short list of the decisions the document asks readers to make, each with a named decision-maker and a date, so that review meetings end with outcomes. Also add a short section for non-functional needs such as performance, accessibility and privacy, with questions to ask for each.
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.