Skills

Skill 63 of 200

Breakdown Epic Pm

Prompt for creating an Epic Product Requirements Document (PRD) for a new epic.

1 minute · 307 words · 13 sections

Install

$ npx skills add github/awesome-copilot --skill breakdown-epic-pm

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Epic Product Requirements Document (PRD) Prompt

Goal

Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to translate high-level ideas into detailed Epic-level Product Requirements Documents (PRDs). These PRDs will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical architecture specification for the epic.

Review the user’s request for a new epic and generate a thorough PRD. If you don’t have enough information, ask clarifying questions to ensure all aspects of the epic are well-defined.

Output Format

The output should be a complete Epic PRD in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/epic.md.

PRD Structure

1. Epic Name

A clear, concise, and descriptive name for the epic.

2. Goal

Problem: Describe the user problem or business need this epic addresses (3-5 sentences).
Solution: Explain how this epic solves the problem at a high level.
Impact: What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, revenue)?

3. User Personas

Describe the target user(s) for this epic.

4. High-Level User Journeys

Describe the key user journeys and workflows enabled by this epic.

5. Business Requirements

Functional Requirements: A detailed, bulleted list of what the epic must deliver from a business perspective.
Non-Functional Requirements: A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).

6. Success Metrics

Key Performance Indicators (KPIs) to measure the success of the epic.

7. Out of Scope

Clearly list what is not included in this epic to avoid scope creep.

8. Business Value

Estimate the business value (e.g., High, Medium, Low) with a brief justification.

Context Template

Epic Idea: [A high-level description of the epic from the user]
Target Users: [Optional: Any initial thoughts on who this is for]

About this skill

Trigger

Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “13 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

A clear, concise, and descriptive name for the epic.

2. Goal

Problem: Describe the user problem or business need this epic addresses (3-5 sentences).
Solution: Explain how this epic solves the problem at a high level.
Impact: What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, revenue)?

3. User Personas

Describe the target user(s) for this epic.

4. High-Level User Journeys

Describe the key user journeys and workflows enabled by this epic.

5. Business Requirements

Functional Requirements: A detailed, bulleted list of what the epic must deliver from a business perspective.
Non-Functional Requirements: A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).

6. Success Metrics

Key Performance Indicators (KPIs) to measure the success of the epic.

7. Out of Scope

Clearly list what is not included in this epic to avoid scope creep.

8. Business Value

Estimate the business value (e.g., High, Medium, Low) with a brief justification.

Context Template

Epic Idea: [A high-level description of the epic from the user]
Target Users: [Optional: Any initial thoughts on who this is for]