Skip to content
Back to skills

Breakdown Epic Pm

ASecurity

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.

  • 38,521 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 6, 2026
ai-agentsgosecurityperformance

Security analysis

A100/100

Scanned June 6, 2026

npx -y skills add github/awesome-copilot --skill breakdown-epic-pm --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Breakdown Epic Pm?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Breakdown Epic Pm
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/github-breakdown-epic-pm/badge)](https://www.skillsdirectory.com/skills/github-breakdown-epic-pm)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: breakdown-epic-pm
description: '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.'
---

# 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]

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.