prd

# PRD Generator Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation. After PRD is confirmed, use `/to-issues` to decompose it into Issues, and optionally `/prd-to-spec` for technical design before that. --- ## The Job 1. Receive a feature description from the user 2. Ask clarifying questions to cover key ambiguities — scale the count to complexity, not a fixed number (see Step 1) 3. Generate a structured PRD based on answers 4. **Present PRD to user for review** — ask "Please review the PRD. Let me know if any adjustments are needed, or reply OK to confirm." 5. Apply any adjustments, then save to `tasks/prd-[feature-name].md` 6. **Suggest next steps** (see Step 3) **Important:** Do NOT start implementing. Just create the PRD. --- ## Step 1: Clarifying Questions Ask only critical questions where the initial prompt is ambiguous. **Scale the number of questions to the feature's complexity — the goal is covering key ambiguities, not hitting a fixed count:** - **Simple, well-scoped feature:** 2-3 questions - **Typical feature:** 3-5 questions - **Complex feature** (multiple user roles, cross-system integration, significant ambiguity): 6-8 questions If a dimension is already unambiguous from the user's input, skip it — don't ask filler questions just to reach a number. Focus on: - **Problem/Goal:** What problem does this solve? - **Core Functionality:** What are the key actions? - **Scope/Boundaries:** What should it...