Skip to content
AI & Agents
Skill

/breakdown-epic-pm

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.

From plugin
awesome-copilot
39k200 skills200 agents
Install
$ npx -y skills add github/awesome-copilot --skill breakdown-epic-pm --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/breakdown-epic-pm

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

breakdown-epic-pm.SKILL.md
name: breakdown-epic-pm
description: '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]
Read more
Ships withawesome-copilot

A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.

Get the whole plugin

Other skills on awesome-copilot.