breakdown-epic-pm▌
github/awesome-copilot · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Structured prompt for generating Epic-level Product Requirements Documents with consistent output format.
- ›Guides product managers through a standardized PRD structure covering goals, user personas, journeys, functional and non-functional requirements, success metrics, and scope boundaries
- ›Outputs markdown-formatted PRDs saved to a consistent directory path ( /docs/ways-of-work/plan/{epic-name}/epic.md ) for use as single source of truth
- ›Includes built-in prompting for clarifying ques
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]
How to use breakdown-epic-pm on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add breakdown-epic-pm
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches breakdown-epic-pm from GitHub repository github/awesome-copilot and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate breakdown-epic-pm. Access the skill through slash commands (e.g., /breakdown-epic-pm) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★73 reviews- ★★★★★Charlotte Diallo· Dec 24, 2024
breakdown-epic-pm is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ganesh Mohane· Dec 20, 2024
breakdown-epic-pm is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Luis Lopez· Dec 20, 2024
Solid pick for teams standardizing on skills: breakdown-epic-pm is focused, and the summary matches what you get after install.
- ★★★★★Mei White· Dec 16, 2024
breakdown-epic-pm fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Charlotte Okafor· Dec 12, 2024
Useful defaults in breakdown-epic-pm — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Alexander Gill· Dec 12, 2024
breakdown-epic-pm reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina Thomas· Nov 23, 2024
Keeps context tight: breakdown-epic-pm is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yash Thakker· Nov 19, 2024
Keeps context tight: breakdown-epic-pm is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sophia Ndlovu· Nov 15, 2024
I recommend breakdown-epic-pm for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ava Menon· Nov 15, 2024
breakdown-epic-pm fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 73