generate-epics

Translate product intent or PRD into 3–7 outcome-driven Epics.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill generate-epics-petrsimonidesxart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-epics
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/discovery/generate-epics
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill generate-epics-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate a product intent or PRD into a concise set of outcome-focused Epics (3–7 max), enabling focused planning and delivery.

Core Features & Use Cases

  • Generate 3–7 outcome-driven Epics from a product intent or PRD.
  • Enforce an Epic-ID collision guard by checking backlog and existing epics.
  • Output Epics using the canonical template for easy import into the backlog.

Quick Start

Provide a product intent or PRD and ask to translate it into 3–7 outcome-driven Epics.

Frequently Asked Questions about generate-epics

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

FAQPage Schema
How do I translate a PRD into actionable epics for my product backlog?

To translate a PRD into actionable epics, provide the product intent or PRD to generate a concise set of 3 to 7 outcome-driven epics ready for focused planning and backlog import.

What is the best way to structure epics when adding a significant feature domain?

The best way to structure epics for a new feature domain is to limit the scope to a maximum of 7 outcome-driven epics, ensuring focused planning and delivery without backlog bloat.

How do you prevent epic ID collisions when generating new backlog items?

Preventing epic ID collisions involves scanning the existing backlog and current epics before generation, enforcing a strict collision guard to maintain unique identifiers across the product roadmap.

Can I use a canonical template for epics to ensure consistent scoping across roadmapping?

Yes, you can enforce a canonical epic template during scoping to ensure consistent structure across roadmapping, making the generated outcomes easy to import directly into the backlog.

When should I restructure my product scope into a smaller set of outcome-driven epics?

You should restructure product scope into outcome-driven epics when starting a new product, adding a significant feature domain, or breaking down a PRD, limiting output to 3 to 7 epics maximum.