breakdown-epic-pm
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.
Profile →npx skills add github/awesome-copilot --skill breakdown-epic-pm --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 epi
- Goal
- Output Format
- PRD Structure
- Context Template
What does the breakdown-epic-pm skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill breakdown-epic-pm --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.