deliver-prd

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Product Requirements Document (PRD)
3 
4A 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.
5 
6## When to Use
7 
8- After problem and solution alignment, before engineering work begins
9- When specifying features, epics, or product initiatives for handoff
10- When multiple teams need to coordinate on a shared deliverable
11- When stakeholders need to approve scope before investment
12- As reference documentation during development and QA
13 
14## When NOT to Use
15 
16- The problem is still unframed or contested -> use `define-problem-statement` first; a PRD assumes an agreed problem
17- You need a one-page pitch to align stakeholders on an approach -> use `develop-solution-brief`; the PRD comes after that alignment
18- You only need the work broken into tickets for a sprint -> use `deliver-user-stories`
19- You are recording a technical or architectural decision -> use `develop-adr`
20 
21## Instructions
22 
23When asked to create a PRD, follow these steps:
24 
251. **Summarize the Problem**
26…