breakdown-epic-pm

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of detailed Epic Product Requirements Documents (PRDs) for large-scale SaaS platforms, ensuring clarity and completeness for engineering teams.

Core Features & Use Cases

  • PRD Generation: Creates comprehensive PRDs from high-level epic ideas.
  • Structured Output: Follows a defined PRD structure including goals, personas, requirements, and success metrics.
  • Use Case: A Product Manager can input a brief idea for a new user authentication system and receive a fully-formed PRD to guide the development process.

Quick Start

Use the breakdown-epic-pm skill to generate a PRD for a new feature that allows users to export their data.

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 complete Epic PRD for a SaaS feature from a brief idea?

Generating an Epic PRD for SaaS from a brief idea requires translating high-level concepts into structured specifications. This Skill automates that process, transforming a simple feature description into a comprehensive document covering problem statements, solutions, and success metrics.

What sections should be included in a large-scale SaaS Product Requirements Document?

A SaaS Product Requirements Document should include problem, solution, impact, user personas, journeys, business requirements, success metrics, out of scope, and business value. This Skill enforces that defined structure to ensure engineering teams receive complete technical architecture inputs.

How do I translate high-level product ideas into detailed engineering specifications?

Translating high-level product ideas into engineering specifications involves defining user journeys and business requirements. This Skill facilitates the breakdown by mapping conceptual features into structured PRD sections, ensuring development teams have clear, actionable technical inputs.

Can I use this PRD generation process for large-scale SaaS platform epics?

This PRD generation process is specifically designed for large-scale SaaS platform epics. It structures comprehensive documents that define business value and success metrics, serving as direct input for complex technical architecture planning within extensive SaaS environments.

What is the best way to structure success metrics and business value in a PRD?

Structuring success metrics and business value in a PRD requires clearly defining impact and measurable goals. This Skill generates documents that explicitly separate business value and success metrics sections, ensuring engineering and product teams align on expected outcomes.