Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

PRD Generator Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation. The Job 1. Receive a feature description from the user 2. Ask 3 5 essential clarifying questions (with lettered options) 3. Generate a structured PRD based on answers 4. Save to tasks/prd [feature name].md Important: Do NOT start implementing. Just create the PRD. Step 1: Clarifying Questions Ask only critical questions where the initial prompt is ambiguous. Focus on: Problem/Goal: What problem does this solve? Core Functionality: What are the key actions? Scope/Boundaries: What should it NOT do? Success Criteria: How do we know it's done? Format Questions Like This: This lets users respond with "1A, 2C, 3B" for quick iteration. Remember to indent the options. Step 2: PRD Structure Generate the PRD with these sections: 1. Introduction/Overview Brief description of the feature and the problem it solves. 2. Goals Specific, measurable objectives (bullet list). 3. User Stories Each story needs: Title: Short descriptive name Description: "As a [user], I want [feature] so that [benefit]" Acceptance Criteria: Verifiable checklist of what "done" means Each story should be small enough to implement in one focused session. Format: Important: Acceptance criteria must be verifiable, not vague. "Works correctly" is bad. "Button shows confirmation dialog before deleting" is good. For any story with UI changes: Always include "Verify in browser using dev browser skill" as acceptance criteria. This ensures visual verification of frontend work. 4. Functional Requirements Numbered list of specific functionalities: "FR 1: The system must allow users to..." "FR 2: When a user clicks X, the system must..." Be explicit and unambiguous. 5. Non Goals (Out of Scope) What this feature will NOT include. Critical for managing scope. 6. Design Considerations (Optional) UI/UX requirements Link to mockups if available Relevant existing components to reuse 7. Technical Considerations (Optional) Known constraints or dependencies Integration points with existing systems Performance requirements 8. Success Metrics How will success be measured? "Reduce time to complete X by 50%" "Increase conversion rate by 10%" 9. Open Questions Remaining questions or areas needing clarification. Writing for Junior Developers The PRD reader may be a junior developer or AI agent. Therefore: Be explicit and unambiguous Avoid jargon or explain it Provide enough detail to understand purpose and core logic Number requirements for easy reference Use concrete examples where helpful Output Format: Markdown ( .md ) Location: tasks/ Filename: prd [feature name].md (kebab case) Example PRD Checklist Before saving the PRD: [ ] Asked clarifying questions with lettered options [ ] Incorporated user's answers [ ] User stories are small and specific [ ] Functional requirements are numbered and unambiguous [ ] Non goals section defines clear boundaries [ ] Saved to tasks/prd [feature name].md