prdlisted

<objective> Interview the user about a feature, then produce a complete product PRD and an ordered task list derived from it, following the flow PRD -> tasks -> (handoff to ship). Stop at the task list; never write feature code. </objective> <parameters> - `<feature idea>`: free-text feature name or one-line idea (remainder of input). - `-a`: auto mode, skip AskUserQuestion confirmations, use recommended options. - `-s`: skip-interview, draft directly from the given idea without the question loop (lower quality, use only when the idea is already detailed). </parameters> <state_variables> - feature_name: string # human-readable feature title - feature_slug: string # kebab-case slug for filenames - answers: object # gathered interview answers (JTBD, user, problem, constraints, 3-dim) - feature_dir: string # docs/prd/<slug>/ (one folder per feature) - prd_path: string # docs/prd/<slug>/prd.md - tasks_path: string # docs/prd/<slug>/tasks.md - prd_body: string # the drafted PRD markdown - task_list: array # ordered tasks derived from the PRD (nested checklist) - auto_mode: boolean # -a - skip_interview: boolean # -s </state_variables> <delimitation> - `prd` != `rfc`: rfc is a technical design doc (alternatives, tradeoffs, architecture). prd stays at product level (user value, scope, metrics) and never picks the technical how. - `prd` != `brainstorm`: brainstorm is open-ended research. prd assumes th