prdlisted

# PRD Writing Skip satisfied steps. If argument provided, skip to Step 2. **Interactive prompts**: present options as a numbered list and wait for the user's choice. ## Input The argument is: $ARGUMENTS If empty, go to Step 1; derive slug after gathering the idea. If provided, derive slug: 1. Take only the text before the first `—` or `–` (if present) 2. Strip leading command verbs: create, build, implement, add, update, fix, make, write, plan, get, show, support 3. Lowercase the text 4. Remove filler words: a, an, the, for, of, to, in, on, with, and, or, but, is, be 5. Take the first 4 remaining words (or fewer if less exist) 6. Join with hyphens → `<slug>` Output: `.tracerkit/prds/<slug>.md`. If file exists, present options and wait: 1. Overwrite existing (Recommended) 2. Pick a new name ## Workflow ### 1. Gather problem description Ask the user for a detailed description of the problem and any solution ideas. ### 2. Explore codebase Map current state: data models, services, API routes, frontend, tests. Note exists vs. must build. **Research protocol**: codebase first, then docs. Unverifiable claims → flag as uncertain, never fabricate. ### 3. Interview One question at a time. Lead with your recommended answer (mark it `(Recommended)` and list first). Explore code instead of asking when possible. Present 2–4 options for each question — structured choices are faster than free-text. | Branch | Key questions | Skip when