Write a Product Requirements Document (PRD) for a New Feature

Draft a Product Requirements Document for the feature '{{feature_name}}' on {{product_name}}. The PRD should include: 1) purpose and context (problem statement and who it serves); 2) user personas and user stories; 3) detailed functional requirements and acceptance criteria; 4) UI/UX notes and edge cases; 5) non-functional requirements (performance, security, compliance); 6) success metrics and how they will be measured; 7) rollout plan and monitoring; 8) dependencies and stakeholders. Keep the PRD structured with clear headings so engineering, design, and QA can act from it.