Breakdown Feature Prd
- 9.8k installs
- 37.1k repo stars
- Updated July 28, 2026
- github/awesome-copilot
A structured, complete Product Requirements Document in Markdown that translates an Epic into actionable feature scope with personas, stories, functional/non-functional requirements, acceptance criteria, and out-of-scope
About
A prompt template that acts as an expert Product Manager to transform Epic-level feature requests into detailed, structured PRDs in Markdown. Developers use it during the planning phase to articulate feature scope, user personas, functional and non-functional requirements, acceptance criteria, and out-of-scope items before engineering work begins. The workflow guides users through clarifying questions, generates PRD output to a standardized file path, and produces artifacts that serve as the single source of truth for downstream technical specification and implementation.
- Generates complete PRD Markdown documents with standard sections: feature name, epic link, goals, personas, user stories
- Prompts for clarifying questions when initial information is incomplete, ensuring thorough feature definition before eng
- Outputs PRD to standardized path structure (/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md) for version contr
- Covers functional, non-functional, and acceptance criteria in checklist/Given-When-Then format for validation and testin
- Positions PRD as single source of truth to feed downstream technical specification and architecture work
Breakdown Feature Prd by the numbers
- 9,798 all-time installs (skills.sh)
- +41 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #94 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
breakdown-feature-prd capabilities & compatibility
- Capabilities
- transform high level epic into detailed feature · elicit missing requirements through clarifying q · generate user stories in standardized format · define both functional and non functional requir · create acceptance criteria in given when then or · establish scope boundaries and out of scope item · output prd in markdown with standard file path s
What breakdown-feature-prd says it does
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 Documen
This PRD will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical specification.
The output should be a complete PRD in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md`.
npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-prdAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 9.8k |
|---|---|
| repo stars | ★ 37.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | github/awesome-copilot ↗ |
What it does
Generate structured Product Requirements Documents for new features from high-level Epic descriptions.
Who is it for?
Teams practicing formal product management; large SaaS platforms with multiple Epic-level features in flight; organizations requiring documented requirements for compliance or handoff.
Skip if: Rapid prototyping, skunkworks, or teams where Product and Engineering are the same person.
When should I use this skill?
A new feature request arrives from stakeholders, roadmap, or customer feedback and needs to be broken down into engineering-ready specifications.
What you get
Teams produce documented, agreed-upon feature requirements before engineering begins, reducing rework and aligning implementation with product intent.
- PRD Markdown document
- User stories in As-a-I-want-so-that format
- Functional requirements checklist
By the numbers
- PRD structure includes 8 major sections (Feature Name, Epic, Goal, Personas, User Stories, Requirements, Acceptance Crit
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]
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Pick breakdown-feature-prd over architecture or ADR skills when the gap is product scope, not a technical decision record.
FAQ
What should I provide to start PRD generation?
Provide the parent Epic (link/doc), a high-level feature description, and optionally target user personas. The prompt will ask clarifying questions if information is incomplete.
What does the PRD output include?
Feature name, Epic link, problem/solution/impact, user personas, user stories, functional and non-functional requirements, acceptance criteria in Given-When-Then format, and out-of-scope boundaries.
Where does the PRD get saved?
Output is saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md in Markdown format.
Is Breakdown Feature Prd safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.