breakdown-epic-pm

To generate a PRD for a new epic, you provide a high-level idea and the skill translates it into a detailed Epic Product Requirements Document, including problem statements, user journeys, and business requirements.

An Epic PRD for technical architecture includes defined sections such as user personas, solution details, business and non-functional requirements, success metrics, out-of-scope items, and business value.

Yes, you can use this PRD generation process for SaaS platform feature planning to automatically capture detailed product requirements that serve as the foundation for engineering teams to create technical specifications.

To structure user personas and requirements for product management documentation, the skill acts as an expert Product Manager and automatically organizes high-level inputs into structured categories like user journeys and success metrics.

No, you do not need technical specifications before creating an Epic PRD; the generated PRD actually serves as the necessary input and foundation for the engineering team to subsequently create technical architecture specifications.

The best way to document out-of-scope items and success metrics for an epic is to use a structured PRD template that explicitly defines these boundaries alongside business value to ensure clear technical planning.