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.
Best use case
breakdown-epic-pm is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using breakdown-epic-pm should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/breakdown-epic-pm/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How breakdown-epic-pm Compares
| Feature / Agent | breakdown-epic-pm | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this 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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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]Related Skills
gitlab-epic-creator
Gitlab Epic Creator - Auto-activating skill for Enterprise Workflows. Triggers on: gitlab epic creator, gitlab epic creator Part of the Enterprise Workflows skill category.
breakdown-plan
Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.
breakdown-feature-prd
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.
breakdown-epic-arch
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
epic-design
Build immersive, cinematic 2.5D interactive websites using scroll storytelling, parallax depth, text animations, and premium scroll effects — no WebGL required. Use this skill for any web design task: landing pages, product sites, hero sections, scroll animations, parallax, sticky sections, section overlaps, floating products between sections, clip-path reveals, text that flies in from sides, words that light up on scroll, curtain drops, iris opens, card stacks, bleed typography, and any site that should feel cinematic or premium. Trigger on phrases like "make it feel alive", "Apple-style animation", "sections that overlap", "product rises between sections", "immersive", "scrollytelling", or any scroll-driven visual effect. Covers 45+ techniques across 8 categories. Always inspects, judges, and plans assets before coding. Use aggressively for ANY web design task.
executing-epic-workflow
Execute systematic feature development using EPIC methodology (Explore, Research, Plan, Validate, Implement, Review, Iterate). Use when building features, implementing complex tasks, or following structured development workflows. Delegates exploration, research, planning, validation, and review to specialized agents.
prd-epic-writer
Convert a discovery document into a structured PRD-level Epic draft for Linear. Use when a validated product idea is scoped as a larger, complex work item with meaningful UX impact.
jira-epic
Creates Jira epics for large features following Prowler's standard format. Trigger: When user asks to create an epic, large feature, or multi-task initiative.
epic-games-automation
Automate Epic Games tasks via Rube MCP (Composio). Always search tools first for current schemas.
Daily Logs
Record the user's daily activities, progress, decisions, and learnings in a structured, chronological format.
Socratic Method: The Dialectic Engine
This skill transforms Claude into a Socratic agent — a cognitive partner who guides
Sokratische Methode: Die Dialektik-Maschine
Dieser Skill verwandelt Claude in einen sokratischen Agenten — einen kognitiven Partner, der Nutzende durch systematisches Fragen zur Wissensentdeckung führt, anstatt direkt zu instruieren.