deliver-prd

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Product Requirements Document (PRD) A Product Requirements Document is the primary specification artifact that communicates what to build and why. It bridges the gap between problem understanding and engineering implementation by providing clear requirements, success criteria, and scope boundaries. A good PRD enables engineering to build the right thing while maintaining flexibility on implementation details. ## When to Use - After problem and solution alignment, before engineering work begins - When specifying features, epics, or product initiatives for handoff - When multiple teams need to coordinate on a shared deliverable - When stakeholders need to approve scope before investment - As reference documentation during development and QA ## Instructions When asked to create a PRD, follow these steps: 1. **Summarize the Problem** Start with a brief recap of the problem being solved. Link to the problem statement if available. Ensure readers understand *why* this work matters before diving into *what* to build. 2. **Define Goals and Success Metrics** Articulate what success looks like. Include specific, measurable metrics with baselines and targets. These metrics should connect directly to the problem being solved. 3. **Outline the Solution** Describe the proposed solution at a high level. Focus on user-facing functionality and key capabilities. Include enough detail for stakeh...