Generating a Product Requirements Document (PRD)

Create a clear, actionable PRD a junior developer can implement without extra context.

When to Use

• Defining feature requirements for a development team
• Turning a product decision or user need into an actionable spec

Input

• Required: Feature description or user request — ideally the approved 1-pager plus the selected solution from solutions/
• Optional: User research, design brief, validated/open assumptions from assumptions/
• Context: company-level-context/product-vision-and-strategy/ for alignment

Output

• Format: Markdown — Location: prd/ (the initiative's prd/ directory; consumed by generate-tasks)
• Filename: prd-[feature-name].md

Process