/product-prd — Product Requirements Document

Write structured PRDs that define what to build and why. PRDs are product-focused — they describe the problem, users, and requirements without prescribing technical implementation.

When to Use

• User says "write a PRD", "product requirements", "feature spec"
• After a brainstorm session, to formalize requirements
• When a feature idea needs to be documented before building

Process

Step 1: Gather Context

Check for existing artifacts:

1. docs/brainstorms/ — Use brainstorm output as starting point
2. User-provided description or $ARGUMENTS
3. If neither exists, ask clarifying questions