agentsclimarketplace
Sign in

Breakdown epic pm

Skill ulpi-io/plugin-marketplace/plugins/github/skills/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 its SKILL.md

Install
npx -y skills add ulpi-io/plugin-marketplace --skill breakdown-epic-pm

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 464 tokens by cl100k_base, as published. Nobody here has run it

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]

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most product spec skills give in 464 tokens

Counted across 483 of the 502 authors here whose files we hold, read 2026-09-06

  • Write the PRD using the templatein 39 of 483, across 36 files
  • Ask one question at a timein 24 of 483
  • Write acceptance criteria in Given-When-Then formatin 24 of 483
  • Write user stories with acceptance criteriain 22 of 483, across 21 files
  • Respect ADRs in areas you touchin 21 of 483, across 17 files
  • Use the domain glossary vocabulary throughout the PRDin 20 of 483, across 16 files
  • Explore the repo to understand the current codebasein 19 of 483, across 15 files
  • Provide testable acceptance criteriain 19 of 483, across 17 files
  • Publish the PRD to the issue trackerin 18 of 483, across 14 files
  • Apply the ready-for-agent triage labelin 15 of 483, across 13 files
  • Prefer existing seams over new onesin 14 of 483, across 12 files
  • Save the PRD as a markdown filehere, and in 14 of 483, across 9 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.