breakdown-epic-pm

Create a Markdown Epic PRD with goals, personas, journeys, and success metrics.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/soham2008xyz/trade-tycoon --skill breakdown-epic-pm-soham2008xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-epic-pm
Source: https://github.com/soham2008xyz/trade-tycoon/tree/main/.agents/skills/breakdown-epic-pm
Command: npx skills add https://github.com/soham2008xyz/trade-tycoon --skill breakdown-epic-pm-soham2008xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you convert a vague epic idea into a detailed Epic Product Requirements Document (PRD) that engineering teams can execute. It reduces back-and-forth by defining goals, personas, journeys, requirements, success metrics, and explicit out-of-scope boundaries. It also ensures the output is formatted and saved in a consistent location for downstream architecture work.

Core Features & Use Cases

  • Epic PRD generation: Produces a complete Epic PRD in Markdown based on the provided epic concept and available context.
  • Clarifying questions when needed: Asks for missing information to ensure the epic is well-defined before finalizing requirements.
  • Architecture-ready output: Structures deliverables so they can be used as input for generating a technical architecture specification.
  • Use case: When stakeholders propose a new feature set for the trading platform, use this skill to produce an engineering-ready PRD that includes measurable success criteria and constraints.

Quick Start

Ask the AI to generate an Epic PRD for your new epic idea and specify any known target users, problem statement, and desired outcomes.

Frequently Asked Questions about breakdown-epic-pm

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

FAQPage Schema
How do I turn an epic idea into a product requirements document for engineering?

Generating an Epic PRD involves defining goals, personas, user journeys, functional and non-functional constraints, success metrics, and explicit out-of-scope items to align stakeholders and prepare for architecture generation.

What should be included in an Epic PRD for a SaaS platform?

An Epic PRD for a SaaS platform should include goals, personas, user journeys, functional and non-functional constraints, measurable success metrics, and explicit out-of-scope boundaries to ensure engineering teams have clear execution parameters.

How do I define out-of-scope items and success metrics for a new feature epic?

To define out-of-scope items and success metrics for a new feature epic, you establish explicit boundaries excluding unrelated features and set measurable criteria to evaluate the epic's impact and stakeholder alignment.

Can I generate architecture input from a product requirements document?

Yes, you can generate architecture input from a product requirements document by structuring the Epic PRD with complete Markdown formatting, ensuring the deliverable is ready for downstream technical architecture specification.

What happens if my epic idea lacks sufficient detail for PRD generation?

If your epic idea lacks sufficient detail for PRD generation, the process pauses and asks clarifying questions to gather missing information about the problem statement and desired outcomes before finalizing requirements.

Does the Epic PRD output support stakeholder alignment for trading platforms?

Yes, the Epic PRD output supports stakeholder alignment for trading platforms by producing an engineering-ready document that includes measurable success criteria and specific non-functional constraints tailored to the platform.