breakdown-epic-pm
Verifiedby github · Updated Apr 16, 2026
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.
See It In Action
Let me explore the codebase first to understand the project and any existing context before drafting the PRD.
I have solid context from the product doc — the pain points, metrics, and current flow are well-defined. Let me draft the PRD.
The PRD is ready at docs/ways-of-work/plan/referral-onboarding-improvements/epic.md.
Here's the summary for your eng planning session:
Epic: Referral Onboarding Improvements for Invited Teams
The core bet is replacing the empty-workspace drop-off (62% never finish Getting Started) with a context-rich onboarding flow powered by three features:
- Starter Kit Builder — referrers attach templates, channels, and a welcome message to their link
- Guided Setup Wizard — invitees land on a personalized page and one-click provision their workspace from the kit
- Referral Dashboard + Nudges — referrers see invitee activation status and can send nudges to re-engage stalled signups
Key targets (90 days): activation rate 15% -> 35%, time-to-value ~6 days -> <1 day, referral NPS 34 -> 45+. Estimated impact: ~$380K+ incremental ARR in year one.
The PRD includes detailed functional/non-functional requirements, analytics instrumentation needs, security constraints (no content leakage from referrer workspaces), and clear out-of-scope items to keep the discussion focused. Let me know if you want to adjust anything before eng picks it up.
Permissions
| Scope | Description |
|---|---|
| filesystem:write |
SKILL.md
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]
FAQ
What does breakdown-epic-pm 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.
When should I use breakdown-epic-pm?
Use it when you need a repeatable workflow that produces text report.
What does breakdown-epic-pm output?
In the evaluated run it produced text report.
How do I install or invoke breakdown-epic-pm?
Ask the agent to use this skill when the task matches its documented workflow.
Which agents does breakdown-epic-pm support?
Agent support is inferred from the source, but not explicitly declared.
What tools, channels, or permissions does breakdown-epic-pm need?
It uses no extra tools; channels commonly include text; permissions include filesystem:write.
Is breakdown-epic-pm safe to install?
Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.
How is breakdown-epic-pm different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does breakdown-epic-pm outperform not using a skill?
About breakdown-epic-pm
When to use breakdown-epic-pm
When you have a new epic idea and need a detailed PRD for engineering handoff. When you want a consistent Markdown template for documenting goals, requirements, metrics, and scope. When the agent should ask clarifying questions before drafting a complete epic specification.
When breakdown-epic-pm is not the right choice
When you need a technical architecture or implementation design rather than a product requirements document. When the task is purely read-only brainstorming and should not create or update files.
What it produces
Produces text report.