breakdown-feature-prd GitHub Copilot skill for PRDs

Q: How do I install breakdown-feature-prd in GitHub Copilot?

Run `gh skill install github/awesome-copilot breakdown-feature-prd`. You can also use `npx skills add github/awesome-copilot --skill breakdown-feature-prd`.

Q: Where does breakdown-feature-prd save the PRD?

It creates the Markdown file at `/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md`.

What breakdown-feature-prd does

This skill turns a feature request and its parent Epic into a detailed Markdown PRD. When the input lacks detail, it asks clarifying questions to define the feature.

It saves the document at /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md. The PRD covers the goal, personas, user stories, functional and non-functional requirements, acceptance criteria, and an Out of Scope section. Acceptance checks can use a checklist or Given/When/Then.

Install it for teams that manage work through Epics and need one requirements document for engineering. For a small task with no Epic, this structure is excessive.

What it helps with

turn a feature idea from an Epic into a PRD
write user stories with acceptance criteria
document functional and non-functional requirements
set feature boundaries in an Out of Scope section
create a Markdown brief for a technical specification

Example prompts for the agent

"Create a PRD for this Epic feature: users need status notifications for their requests."
"Break this Epic into a PRD for data export and ask questions if the context is incomplete."
"Prepare the PRD and save it to `/docs/ways-of-work/plan/payments/refunds/prd.md`."

How to install breakdown-feature-prd

1Skills CLI (Vercel)

npx skills add github/awesome-copilot --skill breakdown-feature-prd

2GitHub CLI

gh skill install github/awesome-copilot breakdown-feature-prd

3Manually: put the files in place

.github/skills/breakdown-feature-prd/SKILL.md

1Skills CLI (Vercel)

npx skills add github/awesome-copilot --skill breakdown-feature-prd -a claude-code

2Manually: put the files in place

~/.claude/skills/breakdown-feature-prd/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/breakdown-feature-prd/

Manually: put the files in place

.agents/skills/breakdown-feature-prd/SKILL.md

For all projects use ~/.agents/skills/

Manually: put the files in place

.cursor/skills/breakdown-feature-prd/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

Platform CLI

gemini skills install https://github.com/github/awesome-copilot --path skills/breakdown-feature-prd

Manually: put the files in place

.devin/skills/breakdown-feature-prd/SKILL.md

The legacy .windsurf/skills/ path still works

From the same set554

The whole set →

git-commit official github This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits. GitHub Copilot 47,165installs excalidraw-diagram-generator official github Turn a plain-language description into an Excalidraw diagram. Useful for mapping processes, system structure, and relationships between entities. GitHub Copilot 31,639installs multi-stage-dockerfile official github This skill guides GitHub Copilot in writing multi-stage Dockerfiles for different languages and frameworks. Use it when the final runtime image should contain fewer build dependencies. GitHub Copilot 29,688installs documentation-writer official github Skill that turns the agent into a technical writer following the Diátaxis framework: tutorials, how-to guides, reference, and explanation. Proposes structure before writing. GitHub Copilot 27,757installs prd official github Turns a feature idea into a structured PRD with user stories, technical requirements, and risks. Use it when planning a software feature or an AI-powered one. GitHub Copilot 24,035installs refactor official github This skill reshapes existing code without changing its external behavior. Use it for gradual cleanup of large functions, duplication, weak types, and code smells. GitHub Copilot 22,321installs java-springboot official github Gives GitHub Copilot Spring Boot development practices, from project layout to tests and security. Use it when writing or reviewing Java application code. GitHub Copilot 21,272installs create-readme official github This skill reviews a project and creates a structured README.md. Use it when the repository needs clear documentation based on its actual files and code. GitHub Copilot 19,081installs

Questions about breakdown-feature-prd

How do I install breakdown-feature-prd in GitHub Copilot?

Run gh skill install github/awesome-copilot breakdown-feature-prd. You can also use npx skills add github/awesome-copilot --skill breakdown-feature-prd.

What does breakdown-feature-prd do?

The skill creates a PRD from an Epic and a feature request. It includes goals, user stories, requirements, acceptance criteria, and scope boundaries.

Where does breakdown-feature-prd save the PRD?

It creates the Markdown file at /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md.

Source text

SKILL.md · MIT

---
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]

breakdown-feature-prd — GitHub Copilot skill

What breakdown-feature-prd does

What it helps with

Example prompts for the agent

How to install breakdown-feature-prd

From the same set554

Similar

Questions about breakdown-feature-prd

Source text

See also