rcode-create-prdlisted

@.rcode/references/karpathy-guidelines.md ## Overview Create a new Product Requirements Document from scratch through guided facilitation. ## Workflow Follow the instructions in ./workflow.md. ## Output Format - Output: PRD file saved to the configured output folder - Structure: Problem → User → Scope → Requirements → Success Metrics → Kill Criteria → Out-of-Scope - Each requirement is quantified (numbers, not adjectives) - Every section has explicit owner and deadline - Do NOT include: vague verbs ("optimize"), unquantified metrics, or requirements without owners ## Fast-path detection If `$ARGUMENTS` or the opening message contains ALL FOUR of these fields, skip the discovery interview and go straight to drafting: | Field | Signal words | |-------|-------------| | Product / feature name | explicit name or noun | | Problem statement | "problem is", "users can't", "currently X fails" | | Target user | "for X users", "persona is", "audience is" | | Scope signal | "must have", "v1 only", "just need", "MVP" | When fast-pathing: confirm detected fields in one line ("Got it — building {name} for {user} to solve {problem}. Starting PRD draft."), then generate without asking further questions. If any of the four are absent, run the normal interview. ## Examples ### Happy Path **Input:** "Create a PRD for a task management feature" **Expected behavior:** Interview user for Problem/User/Scope first. Do NOT start the PRD until all 5 discovery questions are answered. Then d