prd-writerlisted

# PRD Writer Write a PRD for the feature: **$ARGUMENTS** (audience defaults to both engineering and stakeholders) ## Steps 1. **Understand the context** — If a codebase exists, read relevant code to understand current capabilities. Use the feature description to understand the gap. 2. **Define the problem**: - What's the user pain point? - What's the business motivation? - What evidence exists (user feedback, metrics, competitive analysis)? 3. **Define the solution**: - High-level description of what we're building - Key user flows (happy path + error cases) - What's explicitly NOT in scope 4. **Write the PRD**: ```markdown # PRD: <Feature Name> **Author**: <name> **Date**: <date> **Status**: Draft | In Review | Approved ## Problem Statement <2-3 sentences: what's broken or missing, who's affected, why it matters> ## Goals 1. <Primary goal — what success looks like> 2. <Secondary goal> ## Non-Goals - <What we're explicitly NOT doing> - <Adjacent features we're deferring> ## User Stories ### Primary User: <persona> - As a <persona>, I want to <action>, so that <benefit> ### Secondary User: <persona> - As a <persona>, I want to <action>, so that <benefit> ## Proposed Solution ### Overview <1 paragraph description of the approach> ### Key Flows #### Flow 1: <name> 1. User does X 2. System responds with Y 3. User sees Z #### Flow 2: <name> ... ### Technical Considerations - <Architecture impact> - <Data model changes> - <Third-party depend