prdlisted

# prd — writing and extending a format-based requirements document When a PRD is being written or worked on, the material is gathered and analysed first, and the result becomes a **recommended answer**. The user adopts it with a single "go", or writes a different answer instead. Every question carries the option judged most fitting, marked (recommended). A PRD keeps growing. Keep the body thin and push the detail out into the entry list, the tickets, and the design file. **The premise**: external writes happen only after preview → "go". Reading, searching, and gathering come first, without confirmation. ## When to invoke - Writing the requirements for a new product or feature for the first time - Adding entries to an existing PRD, or bringing it in line with what shipped - Design material and meeting notes exist but nothing is in document form yet ## When NOT to invoke - Tidying or auditing a design file → `/fig:prep` · `/fig:lint` - Comparing a shipped screen against the baseline → `/fig:qa` - Filing or syncing tickets → whatever ticket tool you use ## Configuration The rules and values are set by `pm-conventions.yaml`, not by this document. ```bash python3 ${CLAUDE_PLUGIN_ROOT}/_common/scripts/lib/resolve-config.py --name pm-conventions.yaml ``` The layers merge bundled defaults → `~/.claude/pm-conventions.yaml` → `./pm-conventions.yaml`. Later layers cover earlier ones, so **only the keys you need have to be written.** If it ran on bundled defaults alone, say so