Skills github awesome-copilot Epic breakdown workflow

breakdown-feature-prd

Use it when:: You have an epic and want one of its features specified before anyone designs or builds it.
It does:: Acts as a product manager: reviews the feature idea and parent epic, asks clarifying questions if needed, and writes the PRD.
You get:: /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md, with user stories, functional and non-functional requirements, and acceptance criteria.
Unlike prd:: That one, from the same repo, interviews you about a feature on its own; this one starts from an epic and links back to its PRD and architecture documents.

Skill 3 of 6 in the Epic breakdown workflow bundle, after breakdown-epic-arch and before breakdown-feature-implementation.

TL;DR

One of the repo's breakdown prompts, which plan work from an epic down to features, implementation and tests in /docs/ways-of-work/plan/. The agent acts as a product manager for a large SaaS platform: you give it a feature idea, the parent epic and, optionally, the target users, and it asks clarifying questions about anything left undefined. The PRD is meant to be the engineering team's single source of truth and the input for a technical specification. It has eight sections: the feature name; links to the epic's PRD and architecture documents; the goal as problem, solution and expected impact; user personas; user stories in "As a…, I want to…, so that I can…" form, covering main paths and edge cases; functional and non-functional requirements; acceptance criteria for each story or major requirement, as a checklist or Given/When/Then; and what's out of scope.

Summarizes the skill at 797337f.

npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-prd

skills.sh page Source on GitHub All skills from github/awesome-copilot

Total Downloads: 10,100 on skills.sh, Nov 9, 2026
Repo stars: 40,943 github/awesome-copilot
First seen: Feb 25, 2026 on skills.sh

Weekly Downloads

-50% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	24
Sep 28	29
Oct 5	27
Oct 12	11
Oct 19	12
Oct 26	8
Nov 2	15
Nov 9	12

Category	category:planning category:software-engineering Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:command A one-shot action you invoke by name, such as turning the conversation into a PRD.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	requirements planning

SKILL.md

From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: breakdown-feature-prd
description: 'Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.'

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]