breakdown-epic-pm
Structured prompt for generating Epic-level Product Requirements Documents
by githubFree
Description
breakdown-epic-pm is an agent skill from the github/awesome-copilot collection, a structured prompt for writing a product requirements document (PRD) for a new epic, meaning a large body of work for a large-scale software platform. The agent acts as an expert product manager. It turns a high-level idea into a detailed Epic PRD that the engineering team can treat as the single source of truth, and that later feeds the technical architecture specification. The PRD follows a standard structure covering the epic name, its goals, user personas, user journeys, functional and non-functional requirements, success metrics and the scope boundaries that say what is out of scope. If the request does not include enough information, the prompt asks clarifying questions before writing the document, so gaps are surfaced early rather than filled with guesses. The output is a complete Markdown document, saved to a planning folder organized by epic name. The skill is useful for product managers who want a consistent format across many epics, and for teams that want requirements written before design and engineering begin. The PRD still needs the product owner's judgment on priorities and targets, so the metrics and scope should be confirmed with stakeholders. The skill is installed with the skills CLI from the github/awesome-copilot repository. Its skills.sh page showed about 9.1K installs and passing results from three security audits at the time of the scan.…
Highlights
- Standard Epic PRD structure
- Goals, personas, journeys and requirements
- Success metrics and scope boundaries
- Clarifying questions when information is missing
- Markdown output saved by epic name
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate breakdown-epic-pm.
People also visit
breakdown-epic-pm FAQ
What does it produce?
A complete Epic Product Requirements Document in Markdown.
What sections does it cover?
The epic name, goals, user personas, journeys, functional and non-functional requirements, success metrics and scope boundaries.
What if I leave details out?
The prompt asks clarifying questions before it writes the document.
Who should confirm the metrics?
The product owner and stakeholders, because targets and priorities need their judgment.
How do I install it?
Run npx skills add https://github.com/github/awesome-copilot --skill breakdown-epic-pm.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best breakdown-epic-pm alternatives?
Popular alternatives to breakdown-epic-pm include breakdown-feature-prd, prd and product-capability. See all breakdown-epic-pm alternatives