#requirements

Write a detailed PRD for a new feature. Sections: 1. Overview (problem statement, goals, success metrics). 2. User personas and use cases. 3. User stories with acceptance criteria. 4. Functional requirements (detailed specifications). 5. Non-functional requirements (performance, security, scalability). 6. Design mocks and user flows. 7. Technical considerations and dependencies. 8. Launch plan and rollout strategy. 9. Open questions and risks. Use clear, unambiguous language. Collaborate with engineering and design. Keep as living document.

Write clear user stories with testable acceptance criteria. Format: 'As a [persona], I want [functionality], so that [benefit].' Example: 'As a returning customer, I want to save my payment information, so that I can checkout faster on future purchases.' Acceptance criteria using Given-When-Then: Given I'm a logged-in user, When I reach checkout with previously saved payment methods, Then I should see my saved cards as options, And I can select one with a single click, And the form auto-fills payment details. Include edge cases: expired cards, declined payments, first-time users. Definition of Ready: story has clear acceptance criteria, designs attached, effort estimated, dependencies identified. Definition of Done: feature tested, documented, deployed, analytics tracking added.

Create a comprehensive PRD (Product Requirements Document) template. Sections: 1. Executive Summary (Problem, Solution, Success Metrics). 2. User Stories and Personas. 3. Functional Requirements (Must-have vs Nice-to-have). 4. Technical Constraints and Dependencies. 5. Success Criteria and KPIs. 6. Timeline and Milestones. 7. Open Questions and Risks. Use clear, unambiguous language. Include wireframes placeholders and acceptance criteria for each requirement.

Write comprehensive PRDs for complex product features. PRD structure: 1. Executive Summary (2-3 sentences): what you're building and why. 2. Problem Statement: user pain points with supporting data. 3. Success Metrics: how you'll measure success (leading and lagging indicators). 4. User Stories: core use cases with acceptance criteria. 5. Requirements: functional and non-functional (performance, security). 6. Design Mockups: wireframes or high-fidelity designs. 7. Technical Considerations: architecture, dependencies, risks. 8. Go-to-Market Plan: launch strategy and timeline. 9. Open Questions: items to resolve during development. Review process: stakeholder sign-off from engineering, design, marketing before development starts. Living document: update as requirements evolve, maintain change log. Tools: Confluence, Notion, Google Docs for collaboration. Template ensures nothing falls through cracks on complex projects.