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.
Structured prompt for generating Epic-level Product Requirements Documents with consistent output format.
Guides product managers through a standardized PRD structure covering goals, user personas, journeys, functional and non-functional requirements, success metrics, and scope boundaries Outputs markdown-formatted PRDs saved to a consistent directory path ( /docs/ways-of-work/plan/{epic-name}/epic.md ) for use as single source of truth Includes built-in prompting for clarifying questions when information is incomplete, ensuring comprehensive epic definition before handoff to engineering Designed as input preparation for downstream technical architecture specification generation
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotDeclared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars38.8K
LicenseLICENSE
Default branchmain
Open issues21
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Declared agentsgithub-copilot
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,297 B
docsSUMMARY.md190 B
History
First seen on skills.sh
First recorded snapshot · 9,112 installs
SKILL.md
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]
