breakdown-epic-pm

Generate structured Epic-level PRDs in Markdown from high-level product ideas.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-epic-pm-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-epic-pm
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/breakdown-epic-pm
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-epic-pm-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many high-level product ideas lack a consistent, engineering-ready specification, causing unclear scope, missed requirements, and rework; this Skill standardizes epic-level PRDs so engineering teams have a single source of truth.

Core Features & Use Cases

  • Structured PRD generation: Produces a complete Epic PRD in Markdown with sections for goal, personas, user journeys, business and non-functional requirements, success metrics, out-of-scope items, and business value.
  • Clarification and completeness: Detects missing information and requests clarifying questions to ensure the PRD is actionable for technical architecture and implementation planning.
  • Team handoff: Outputs the PRD in the repository path expected by ways-of-work documentation to streamline handoff to engineering and architecture teams; ideal for large SaaS platform initiatives.

Quick Start

Create an epic PRD for "improved onboarding experience" that includes goal, personas, high-level user journeys, functional and non-functional requirements, success metrics, out-of-scope items, and a business value estimate.

Frequently Asked Questions about breakdown-epic-pm

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

FAQPage Schema
How do I create an engineering-ready PRD from a high-level epic idea?

To convert an epic idea into an engineering-ready PRD, input your high-level product proposal to generate a structured document with goals, personas, user journeys, functional and non-functional requirements, and success metrics.

What should be included in an epic-level product requirements document for a SaaS platform?

An epic-level PRD for a SaaS platform should include the goal, personas, user journeys, functional and non-functional requirements, success metrics, out-of-scope items, and a business value estimate.

How do I translate user proposals into structured requirements for technical architecture teams?

You translate user proposals into structured requirements by processing high-level ideas into a standardized Markdown PRD, serving as a single source of truth for technical architecture and implementation planning.

Can I generate a PRD if my initial product idea or proposal is missing information?

Yes, you can generate a PRD with incomplete information because the process detects missing details and prompts you with clarifying questions to ensure the final document is actionable.

What is the best way to standardize epic PRDs for engineering handoff?

The best way to standardize epic PRDs for engineering handoff is to output the document in the repository path expected by your ways-of-work documentation, streamlining the transition to engineering and architecture teams.