Claude prompt
Claude: Write Product Requirements Document
Full PRD with user stories, acceptance criteria, edge cases, success metrics, and technical considerations.
Write a Product Requirements Document (PRD) for {{feature_name}}. ## Product Context Product: {{product_name}} Current user problem: {{problem}} Proposed solution: {{solution_description}} Target users: {{target_users}} Priority: {{priority}} | Target release: {{target_release}} ### PRD Sections **1. Problem Statement** Articulate the user problem in one clear paragraph. Include quantitative data if available. Why does this problem matter? What is the cost of NOT solving it? **2. Goals and Success Metrics** Primary metric: What single number defines success? Secondary metrics: Supporting indicators Anti-goals: What we are explicitly NOT trying to do with this feature Timeline: When will we measure success? **3. User Stories** Format each as: "As a [user type], I want to [action] so that [outcome]." Cover: primary flow, edge cases, admin/support flows, error states. Minimum 8 user stories. **4. Acceptance Criteria** For each user story, provide testable criteria: - Given [context], when [action], then [expected result] - Cover: happy path, error states, permission edge cases, empty states **5. Technical Considerations** API changes required, database schema impact, performance requirements, security requirements, third-party integrations needed. **6. Design Requirements** Key screens needed (not the design itself — just what screens are required), interaction requirements, accessibility requirements. **7. Out of Scope** Explicit list of what will NOT be built in this version. **8. Open Questions** Unresolved decisions that need stakeholder input.
Fill in: {{feature_name}}, {{product_name}}, {{problem}}, {{solution_description}}, {{target_users}}, {{priority}}, {{target_release}}. In Loopy you fill these in a form and copy the finished prompt in one click.

