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]

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

72/100

Grade

B

Good

Safety

85

Quality

68

Clarity

76

Completeness

62

Summary

This skill provides a structured prompt template for an AI agent acting as a Product Manager to generate Epic-level Product Requirements Documents (PRDs) from high-level epic ideas. The agent interviews users for missing details, synthesizes information into a comprehensive Markdown PRD covering problem, solution, user personas, journeys, business and non-functional requirements, success metrics, scope boundaries, and business value, then saves the output to a project documentation directory.

Detected Capabilities

file writetext generationdocument structuringmarkdown formattinginteractive prompting

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

create epic prdepic requirements documentproduct epic planningdefine epic scopeepic discovery interview

Use Cases

Define scope and requirements for new product epics before technical design
Create a single source of truth document for engineering teams to reference during implementation
Align product and engineering on epic goals, success metrics, and constraints before architecture design begins
Capture business context, user needs, and non-functional requirements in a structured format for downstream artifact generation
Conduct product discovery interviews and transform narrative responses into formal PRD structure

Quality Notes

Skill provides clear PRD structure with well-defined sections (Epic Name, Goal, User Personas, Journeys, Requirements, Success Metrics, Out of Scope, Business Value)
Context template included at the end to guide initial user input
Output path is deterministic and scoped to project documentation directory (/docs/ways-of-work/plan/{epic-name}/epic.md)
No error handling documented for edge cases (missing user input, incomplete information, invalid epic names)
Guidance on asking clarifying questions is vague — no examples of specific questions to ask when information is insufficient
No documentation of limitations (e.g., complexity cap, maximum epic scope, assumptions about team structure)
PRD structure aligns with industry standard (Atlassian, ProductSchool-style PRDs) making it professionally recognized
Missing guidance on versioning, review processes, or how to handle PRD updates after creation

Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

breakdown-epic-pm