Clear PRD

Purpose

Turn an unclear product request into a reviewed product-requirements document before technical design or implementation.

Keep clarification centered on user goals, experience, interactions, workflow, rules, states, exceptions, and acceptance criteria. Avoid implementation tactics unless a technical choice materially changes user-visible product behavior.

Output Location

Preserve the repository's existing PRD convention instead of creating a competing one.

Use this precedence:

1. explicit user-requested path;
2. an existing repository PRD location or documentation contract;
3. fallback prd/YYYY-MM-DD-<short-topic>.md.

For the fallback only, create prd/ when missing. If the path already exists, append -v2, then -v3, and so on. Do not relocate or duplicate an existing PRD solely to match this fallback.