skills.rest
lluppesms
lluppesmsCOMMUNITY
Explore all skills by this author →
GitHub

breakdown-epic-pm

Generate a structured Markdown Epic PRD from epic idea and target user input.

Updated Nov 21, 2025
Search Tags:#documentation#requirements#product management#technical specification#prd#epic
One-click install
npx skills add https://github.com/lluppesms/dadabase.demo --skill breakdown-epic-pm-lluppesms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-epic-pm
Source: https://github.com/lluppesms/dadabase.demo/tree/main/.github/skills/breakdown-epic-pm
Command: npx skills add https://github.com/lluppesms/dadabase.demo --skill breakdown-epic-pm-lluppesms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating high-level epic ideas into detailed Product Requirements Documents (PRDs), ensuring all necessary information is captured for technical architecture.

Core Features & Use Cases

  • PRD Generation: Creates comprehensive Epic PRDs based on user input.
  • Clarifying Questions: Asks for missing information to ensure completeness.
  • Use Case: A product manager has a new feature idea for user profile customization. They use this Skill to generate a full PRD, which then serves as the foundation for the engineering team's technical design.

Quick Start

Use the breakdown-epic-pm skill to create a PRD for an epic named 'User Profile Redesign'.

Frequently Asked Questions about breakdown-epic-pm

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

FAQPage Schema
How do I generate a PRD for an epic feature idea?▼

To generate a PRD for an epic, provide a detailed description of your feature idea and target users. The tool outputs a structured Markdown document containing problem statements, user journeys, business requirements, and success metrics.

What sections are included in a technical specification PRD?▼

A technical specification PRD includes problem statements, proposed solutions, user personas, journeys, business and non-functional requirements, success metrics, scope, and business value to guide engineering architecture.

How do I structure product requirements for technical architecture input?▼

You structure product requirements for technical architecture by defining user personas, journeys, and non-functional requirements in a Markdown PRD. This captures all necessary epic information for engineering teams to design technical specifications.

Can I create an epic PRD with only a high-level feature description?▼

You can start with a high-level feature description, but the tool will ask clarifying questions to gather missing information. Detailed input on the epic idea and target users is required to produce a complete PRD.

What is the best way to document user personas and business value for a new epic?▼

The best way to document user personas and business value for a new epic is using a structured PRD format. This ensures all necessary product management components are captured for downstream technical design and architecture.

Related Skills

Explore More Product & Management Skills→
markarnoldutahmarkarnoldutah

breakdown-epic-pm

Generate a structured Epic Product Requirements Document for SaaS platform epics.

Community
Intermediate
anipatkeanipatke
1

savepoint-system-design

Convert product scope and epic outlines into structured technical design documents.

Community
Intermediate
dhar174dhar174
1

breakdown-epic-pm

Translate user requests into a complete Epic PRD with standard sections.

Community
Advanced
michael-harrismichael-harris
17

devteam-plan

Orchestrate project planning with requirements gathering, codebase research, and PRD generation.

Community
Advanced