skills.rest
ripabak
ripabakCOMMUNITY
Explore all skills by this author →
GitHub

breakdown-epic-pm

Convert vague ideas into a comprehensive Epic PRD for architecture planning.

Updated Apr 25, 2026
Search Tags:#planning#architecture#requirements#prd#epic#product-management#user-personas
One-click install
npx skills add https://github.com/ripabak/elysia-multi-tenancy-template --skill breakdown-epic-pm-ripabak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-epic-pm
Source: https://github.com/ripabak/elysia-multi-tenancy-template/tree/main/.agents/skills/breakdown-epic-pm
Command: npx skills add https://github.com/ripabak/elysia-multi-tenancy-template --skill breakdown-epic-pm-ripabak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This prompt translates vague epic ideas into a thorough Epic Product Requirements Document (PRD) that can be used by engineering and architecture teams as a single source of truth.

Core Features & Use Cases

  • Comprehensive PRD: Generates sections for Epic Name, Goals, Personas, High-level journeys, business and non-functional requirements, success metrics, and scope.
  • Structured guidance: Provides a clear framework to capture acceptance criteria, constraints, and value.
  • Use Case: Given a rough epic concept like "multi-tenant data isolation," produces a complete PRD ready for architectural planning.

Quick Start

Provide a high-level epic idea and receive a complete Epic PRD document ready for architecture planning.

Frequently Asked Questions about breakdown-epic-pm

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

FAQPage Schema
How do I convert a vague product idea into a structured Epic PRD?▼

To convert a vague product idea into an Epic PRD, you provide a high-level concept and the framework generates a comprehensive document covering goals, personas, journeys, functional requirements, metrics, and scope for architecture planning.

What sections should an Epic PRD include for cross-functional planning?▼

An Epic PRD for cross-functional planning should include the epic name, goals, user personas, high-level journeys, business and non-functional requirements, success metrics, scope, and business value to serve as a single source of truth.

Can I use a generated Epic PRD directly for architecture planning?▼

Yes, you can use the generated Epic PRD directly for architecture planning because it explicitly translates rough epic concepts into structured functional and non-functional requirements for engineering teams.

How do I define user personas and success metrics for a new SaaS epic?▼

Defining user personas and success metrics for a new SaaS epic involves capturing the target user roles, mapping their high-level journeys, and establishing measurable criteria to evaluate the epic's business value and scope.

What is the best way to document non-functional requirements for product discovery?▼

The best way to document non-functional requirements during product discovery is to integrate them into a comprehensive Epic PRD, ensuring constraints and acceptance criteria are clearly captured for engineering scoping.

Related Skills

Explore More Product & Management Skills→
TheCraigHewittTheCraigHewitt
131

shape

Convert rough product ideas into structured PRDs via a decision-tree workflow.

Community
Advanced
zhu637882-stackzhu637882-stack

engineer-dev

Translate architectural blueprints into runnable code modules and API designs.

Community
Advanced
EchoNoReturnEchoNoReturn

epic-breakdown-advisor

Break down large epics into end-to-end user stories using nine splitting patterns.

Community
Advanced
michaelboedingmichaelboeding
24

product-engineer-agent

Design comprehensive product specifications from initial ideas.

Community
Advanced