Index of every page on this site: llms.txt
All skills
github avatar

/breakdown-epic-pm

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/breakdown-epic-pm

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈46 tokens for metadata: the name and description. ≈521 when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈185 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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]

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is a prompt template for generating Product Requirements Documents (PRDs) and does not contain any malicious code, network exfiltration, or security vulnerabilities.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 9 months ago

README badge

README badge for github/awesome-copilot/breakdown-epic-pm

Generates an Epic Product Requirements Document (PRD) by prompting for missing details about a new feature or system, then outputting a structured markdown template covering problem, solution, user personas, journeys, functional and non-functional requirements, success metrics, and scope. Designed for product managers preparing input for technical architecture specifications in large-scale SaaS platforms.

Generated from the current SKILL.md.

Does this skill generate a technical architecture spec, or just the PRD?
It generates the Epic PRD only. The PRD then serves as input for a separate step that generates the technical architecture specification.
What format does the output PRD use?
Markdown, saved to `/docs/ways-of-work/plan/{epic-name}/epic.md`.
Will the skill ask clarifying questions if the epic idea is incomplete?
Yes. If you don't provide enough information, the skill will prompt for clarifications to ensure all aspects of the epic are well-defined before generating the PRD.
Does this skill work for any type of SaaS epic, or is it domain-specific?
It is designed as a general-purpose Product Manager prompt for large-scale SaaS platforms and should work across different domains, though it does not tailor itself to specific industries.

Generated from the current SKILL.md. These answers refresh after source changes.