Breakdown Feature Prd

1---2name: breakdown-feature-prd3description: 'Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.'4---5 6# Feature PRD Prompt7 8## Goal9 10Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to take a high-level feature or enabler from an Epic and create a detailed Product Requirements Document (PRD). This PRD will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical specification.11 12Review the user's request for a new feature and the parent Epic, and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the feature are well-defined.13 14## Output Format15 16The output should be a complete PRD in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md`.17 18### PRD Structure19 20#### 1. Feature Name21 22- A clear, concise, and descriptive name for the feature.23 24#### 2. Epic25 26- Link to the parent Epic PRD and Architecture documents.27 28#### 3. Goal29 30- **Problem:** Describe the user problem or business need this feature addresses (3-5 sentences).31- **Solution:** Explain how this feature solves the problem.32- **Impact:** What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, etc.)?33 34#### 4. User Personas35 36- Describe the target user(s) for this feature.37 38#### 5. User Stories39 40- Write user stories in the format: "As a `<user persona>`, I want to `<perform an action>` so that I can `<achieve a benefit>`."41- Cover the primary paths and edge cases.42 43#### 6. Requirements44 45- **Functional Requirements:** A detailed, bulleted list of what the system must do. Be specific and unambiguous.46- **Non-Functional Requirements:** A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).47 48#### 7. Acceptance Criteria49 50- For each user story or major requirement, provide a set of acceptance criteria.51- Use a clear format, such as a checklist or Given/When/Then. This will be used to validate that the feature is complete and correct.52 53#### 8. Out of Scope54 55- Clearly list what is _not_ included in this feature to avoid scope creep.56 57## Context Template58 59- **Epic:** [Link to the parent Epic documents]60- **Feature Idea:** [A high-level description of the feature request from the user]61- **Target Users:** [Optional: Any initial thoughts on who this is for]