AutoGineer
Generated banner for Breakdown Epic Pm
Generated logo for Breakdown Epic Pm

Breakdown Epic Pm

GitHubOfficialOriginally contributed by @craigbekker as prompts/breakdown-epic-pm.prompt.md; moved into a skill by pull request #761Distributed by GitHub

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by craigbekker

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as an expert Product Manager to transform high-level feature ideas into comprehensive Epic Product Requirements Documents (PRDs). It provides a structured framework that ensures all necessary business, functional, and non-functional requirements are captured, serving as a foundation for subsequent technical architecture planning.

What it does

  • Generates a structured Epic PRD in Markdown format.
  • Defines core problem statements, proposed solutions, and expected business impact.
  • Identifies target user personas and key user journeys.
  • Outlines detailed functional and non-functional requirements.
  • Establishes success metrics and defines project scope boundaries.
  • Prompts the user for clarifying information if the initial request is incomplete.

When to use it

  • When you need to formalize a new feature idea into a structured document.
  • When preparing requirements to be handed off for technical architecture design.
  • When you need to ensure alignment on project scope and success criteria.
  • When you need to document non-functional constraints like security or accessibility.

Advantages

  • Ensures consistency in documentation across different epics.
  • Helps prevent scope creep by explicitly defining out-of-scope items.
  • Provides a clear source of truth for engineering and product teams.
  • Facilitates better communication of business value and user impact.

Usage examples

“Create an Epic PRD for a new user notification system.”
The agent generates a structured PRD document detailing the notification system's goal, user personas, functional requirements, and success metrics.
“I need a PRD for an integrated billing dashboard.”
The agent produces a comprehensive document outlining the billing dashboard's business value, user journeys, and technical constraints.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/breakdown-epic-pm/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip breakdown-epic-pm.zip -d .agents/skills

Documentation by craigbekker

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]

Files

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Originally contributed by
GitHub avatar of craigbekker@craigbekkeras prompts/breakdown-epic-pm.prompt.mdmoved into a skill by pull request #761
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/breakdown-epic-pm · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
craigbekker

AutoGineer is not affiliated with or endorsed by craigbekker or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download breakdown-epic-pm.zip