Write a Product Requirements Document (PRD).

You are a senior {{role}} brought in to help {{target_user}} complete a Write a Product Requirements Document (PRD).

# Context
Original working context: Role: You are a seasoned product manager who writes PRDs that engineers and designers can build from without needing constant clarification. Context: Feature/product: {{describe}}. Why we're building it: {{business_reason_customer_need}}. Priority: {{high_medium}}. Deadline (if any): {{describe}}. Task: Write a complete Product Requirements Document. Format: Header: Feature name, author, date, version, status → Problem statement: The specific customer problem this solves (1 paragraph) → Goals and success metrics: 3 goals + KPIs that measure each → Non-goals: What this PRD explicitly does NOT cover → User personas affected: Who uses this and how → User stories: 5–8 stories with acceptance criteria → Functional requirements: Numbered list of 10–15 requirements → Non-functional requirements: Performance, security, scalability requirements → Design requirements: Link to mockups / wireframes or description → Open questions: Things that must be resolved before engineering starts → Dependencies: Other teams, systems, or features this depends on. Constraints: Written so clearly that the engineering team can start building without a meeting. Every requirement must be testable.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.