PRD First Draft

Generate a complete, engineer-ready Product Requirements Document from a feature brief, covering user stories, functional requirements, and open questions.

Product ManagerClaudeChatGPTGeminiLowUpdated Mar-26

232·

Prompt

Write a detailed Product Requirements Document (PRD) for the following feature: Feature Name: User Problem: Target User: Business Context: Assumptions & Constraints: Please structure the PRD with the following sections: Overview: A 3–4 sentence summary of the feature, the problem it solves, and why it matters now Goals & Non-Goals: Explicit list of what success looks like, and what this feature will deliberately not do. User Stories: Written in "As a , I want to so that " format; cover the core happy path and at least two edge cases. Functional Requirements: Numbered list of specific behaviours the system must support, written so an engineer can estimate against them. Success Metrics: Primary metric: . Include how it will be measured, current baseline, and target. Design & UX Considerations: Key user experience principles or constraints the designer should know upfront. Dependencies & Risks: Any teams, systems, or decisions this feature relies on; flag the top 2–3 risks. Open Questions: Unresolved decisions with a named owner and a due date for each. Out of Scope: Explicit list of related ideas that are not part of this version. Keep language precise and scannable. This will be read by engineers, designers, and stakeholders. Avoid vague language like "improve" or "enhance"; use measurable and specific terms throughout.