Epic Product Requirements Document
OfficialFreeStreamline your epic PRD creation process.
Free · Opens the source repo
What Epic Product Requirements Document does
The Epic Product Requirements Document (PRD) skill is designed to assist Product Managers in creating comprehensive PRDs for large-scale SaaS platforms. This skill transforms high-level ideas into detailed documents that serve as a single source of truth for engineering teams. By following a structured format, it ensures that all necessary components of a PRD are covered, facilitating better communication and understanding among stakeholders.
When using this skill, users will be prompted to provide details about the new epic they wish to develop. The skill will guide them through the process of defining the epic's name, goals, user personas, high-level user journeys, business requirements, success metrics, and more. If the initial information is insufficient, the skill will ask clarifying questions, ensuring that every aspect of the epic is well-defined before generating the final document.
The output is formatted in Markdown and saved in a specified directory, making it easy to integrate into existing documentation workflows. This skill is particularly useful for teams looking to standardize their PRD creation process and ensure that all critical elements are included, reducing the risk of scope creep and miscommunication.
Ideal for Product Managers, this skill is a valuable addition to any development team's toolkit, enhancing productivity and clarity in project planning.
When to use it
Use this skill when you need to create a detailed PRD for a new epic, especially in a collaborative environment where clarity is crucial.
When not to use it
This skill may not be suitable for small projects or teams that do not require formalized documentation processes.
What you can build with it
Creating a New Epic PRD
When starting a new project, use this skill to define the epic's goals and requirements clearly.
Standardizing PRD Documentation
Implement this skill across your team to ensure consistency in how PRDs are created and documented.
Facilitating Team Collaboration
Use this skill to gather input from various stakeholders, ensuring all perspectives are considered in the PRD.
How to install Epic Product Requirements Document
View source1. Install with the skills CLI
npx skills add github/awesome-copilot/breakdown-epic-pm --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by githubEpic 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]
Frequently asked questions about Epic Product Requirements Document
Similar skills
Competitive Analysis
Build detailed competitive landscape decks efficiently.
Brand Discovery
Structured interviews to articulate brand identity.
CrossFrame Org
Facilitates structured organizational analysis and repair.
Technical Product Pricing
Optimize your pricing strategy for technical products.
Product-Led Growth
Optimize your go-to-market strategy with data-driven insights.
Positioning Strategy
Own your market position with clear differentiation.