{"kind":"Skill","metadata":{"namespace":"community","name":"breakdown-feature-prd","version":"0.1.0"},"spec":{"description":"Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.","files":{"SKILL.md":"---\nname: breakdown-feature-prd\ndescription: 'Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.'\n---\n\n# Feature PRD Prompt\n\n## Goal\n\nAct 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.\n\nReview 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.\n\n## Output Format\n\nThe output should be a complete PRD in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md`.\n\n### PRD Structure\n\n#### 1. Feature Name\n\n- A clear, concise, and descriptive name for the feature.\n\n#### 2. Epic\n\n- Link to the parent Epic PRD and Architecture documents.\n\n#### 3. Goal\n\n- **Problem:** Describe the user problem or business need this feature addresses (3-5 sentences).\n- **Solution:** Explain how this feature solves the problem.\n- **Impact:** What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, etc.)?\n\n#### 4. User Personas\n\n- Describe the target user(s) for this feature.\n\n#### 5. User Stories\n\n- Write user stories in the format: \"As a `\u003cuser persona\u003e`, I want to `\u003cperform an action\u003e` so that I can `\u003cachieve a benefit\u003e`.\"\n- Cover the primary paths and edge cases.\n\n#### 6. Requirements\n\n- **Functional Requirements:** A detailed, bulleted list of what the system must do. Be specific and unambiguous.\n- **Non-Functional Requirements:** A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).\n\n#### 7. Acceptance Criteria\n\n- For each user story or major requirement, provide a set of acceptance criteria.\n- 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.\n\n#### 8. Out of Scope\n\n- Clearly list what is _not_ included in this feature to avoid scope creep.\n\n## Context Template\n\n- **Epic:** [Link to the parent Epic documents]\n- **Feature Idea:** [A high-level description of the feature request from the user]\n- **Target Users:** [Optional: Any initial thoughts on who this is for]\n"},"import":{"commit_sha":"541b7819d8c3545c6df122491af4fa1eae415779","imported_at":"2026-05-18T20:05:35Z","license_text":"MIT License\n\nCopyright GitHub, Inc.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.","owner":"github","repo":"github/awesome-copilot","source_url":"https://github.com/github/awesome-copilot/tree/541b7819d8c3545c6df122491af4fa1eae415779/plugins/project-planning/skills/breakdown-feature-prd"}},"content_hash":[194,93,59,121,128,153,161,78,80,16,81,181,221,59,31,244,20,50,199,194,26,150,80,186,182,47,0,205,217,51,135,57],"trust_level":"unsigned","yanked":false}