breakdown-epic-pm

Generates an Epic Product Requirements Document in Markdown from a high-level epic idea.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-epic-pm-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-epic-pm
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/breakdown-epic-pm
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-epic-pm-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers often struggle to translate vague, high-level ideas into structured Epic PRDs that engineering teams can act on. This Skill provides a consistent, complete PRD template covering goals, personas, requirements, and success metrics. ## Core Features & Use Cases - Structured Epic PRD Generation: Produces a complete PRD with sections for goal, user personas, user journeys, business requirements, success metrics, scope, and business value. - Clarifying Questions: Prompts for missing information when the epic idea is underspecified, ensuring well-defined requirements. - Standardized Output: Saves the PRD to a predictable path (/docs/ways-of-work/plan/{epic-name}/epic.md) for use as input to technical architecture specifications. - Use Case: A product manager receives a stakeholder request like "add team workspaces" and uses this Skill to produce a full Epic PRD ready for engineering review. ## Quick Start Ask the AI to create an Epic PRD for your new epic idea, providing a short description of the epic and its target users.

Frequently Asked Questions about breakdown-epic-pm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an Epic PRD for a new product feature?

Provide a high-level description of the epic and optionally its target users. The Skill generates a complete PRD with goal, personas, user journeys, business requirements, success metrics, out-of-scope items, and business value, saved as Markdown.

What sections should an Epic PRD template include?

This template includes epic name, goal (problem, solution, impact), user personas, high-level user journeys, functional and non-functional business requirements, success metrics (KPIs), out-of-scope items, and a business value estimate.

Where is the generated Epic PRD file saved?

The PRD is saved in Markdown format to /docs/ways-of-work/plan/{epic-name}/epic.md, where {epic-name} is derived from the epic being defined. This path keeps planning documents organized per epic.

What happens if my epic idea is missing details?

The Skill instructs the AI to ask clarifying questions when information is insufficient. This ensures all aspects of the epic are well-defined before the PRD is finalized for engineering handoff.

Can the Epic PRD be used for technical architecture planning?

Yes, the PRD is explicitly designed as input for generating a technical architecture specification. It serves as the single source of truth for the engineering team during epic planning.