How do I install the Breakdown Epic Pm skill?

Run npx skillmds add thedixitjain/breakdown-epic-pm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Breakdown Epic Pm safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Breakdown Epic Pm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Breakdown Epic Pm free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Breakdown Epic Pm?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Breakdown Epic Pm by thedixitjain — Agent Skill

Name: Breakdown Epic Pm
Rating: 4.5 (4 reviews)
Author: thedixitjain

File contents

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]

Source: github/awesome-copilot → skills/breakdown-epic-pm/SKILL.md

---name: breakdown-epic-pmdescription: 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] --- **Source:** [`github/awesome-copilot`](https://github.com/github/awesome-copilot) → `skills/breakdown-epic-pm/SKILL.md`

Frequently asked questions