Breakdown Feature Prd
github/awesome-copilotOfficial
The breakdown-feature-prd skill prompts Claude to act as a Product Manager and generate detailed Product Requirements Documents (PRDs) for new SaaS features based on parent Epics. It's designed for product teams and engineering organizations who need structured, comprehensive feature specifications that include goals, user personas, user stories, functional and non-functional requirements, acceptance criteria, and scope boundaries. This skill solves the problem of inconsistent or incomplete feature documentation by providing a standardized PRD template and guidance that ensures all critical aspects of a feature are defined before engineering work begins.
- installs
- 10K
- GitHub stars
- 40.5K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add github/awesome-copilot --skill breakdown-feature-prd --agent claude-codeInstalls into .claude/skills of the current project.
Files
Feature PRD Prompt
Goal
Act 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.
Review 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.
Output Format
The output should be a complete PRD in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md.
PRD Structure
1. Feature Name
- A clear, concise, and descriptive name for the feature.
2. Epic
- Link to the parent Epic PRD and Architecture documents.
3. Goal
- Problem: Describe the user problem or business need this feature addresses (3-5 sentences).
- Solution: Explain how this feature solves the problem.
- Impact: What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, etc.)?
4. User Personas
- Describe the target user(s) for this feature.
5. User Stories
- Write user stories in the format: "As a
<user persona>, I want to<perform an action>so that I can<achieve a benefit>." - Cover the primary paths and edge cases.
6. Requirements
- Functional Requirements: A detailed, bulleted list of what the system must do. Be specific and unambiguous.
- Non-Functional Requirements: A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).
7. Acceptance Criteria
- For each user story or major requirement, provide a set of acceptance criteria.
- 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.
8. Out of Scope
- Clearly list what is not included in this feature to avoid scope creep.
Context Template
- Epic: [Link to the parent Epic documents]
- Feature Idea: [A high-level description of the feature request from the user]
- Target Users: [Optional: Any initial thoughts on who this is for]
Sponsors
Details
- Repository
- github.com/github/awesome-copilot
- Categories
- Git & Pull Requests, AI & Agent Building, Productivity & Planning
