skills.rest
anderson-0
anderson-0COMMUNITY
Explore all skills by this author →
GitHub

create-epics

Break product requirements into structured epics and user stories with acceptance criteria.

4|2|Updated Apr 1, 2026
Search Tags:#requirements#acceptance criteria#epics#user stories#prd#product planning
One-click install
npx skills add https://github.com/anderson-0/mighty-powers --skill create-epics-anderson-0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/anderson-0/mighty-powers/tree/main/skills/create-epics
Command: npx skills add https://github.com/anderson-0/mighty-powers --skill create-epics-anderson-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams turn product requirements and architecture decisions into organized epics and implementation-ready user stories, reducing ambiguity between planning and development.

Core Features & Use Cases

  • Requirements Decomposition: Extracts functional, non-functional, architecture, and UX requirements into structured planning artifacts.
  • Epic and Story Creation: Organizes work into user-value-focused epics with detailed acceptance criteria suitable for developers.
  • Use Case: A product owner with a PRD and architecture document can use this Skill to create a complete epic breakdown and story backlog before implementation begins.

Quick Start

Use the create-epics skill to transform my product requirements into epics and user stories with acceptance criteria.

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I break down product requirements into epics and user stories?▼

To break down product requirements, this Skill extracts functional, architecture, and UX needs from your PRD, groups them by user value into structured epics, and formats them into implementation-ready user stories.

What is the best way to write testable acceptance criteria for a PRD?▼

Writing testable acceptance criteria involves validating workflows extracted from your product requirements and formatting each user story with clear conditions to ensure development readiness and reduce ambiguity.

Can I use architecture decisions to generate a development roadmap backlog?▼

Yes, you can use architecture decisions alongside UX specifications as input to generate a complete epic breakdown and structured story backlog organized for your development roadmap.

How to extract user stories from a PRD before implementation begins?▼

Extracting user stories from a PRD requires systematic requirement extraction, user-value grouping, and workflow validation to transform raw product planning documents into actionable development tasks.

Does this approach work for organizing non-functional requirements into epics?▼

Yes, this approach organizes non-functional requirements by grouping them into user-value-focused epics alongside functional needs, ensuring all extracted constraints are structured for developers.

When should I not use automated epic breakdown for product planning?▼

You should avoid automated epic breakdown when your product planning lacks clear UX specifications or architecture decisions, as systematic requirement extraction requires defined inputs to generate testable stories.

Related Skills

Explore More Product & Management Skills→
WizarckWizarck

bmad-check-implementation-readiness

Validate PRD, UX, architecture, and epics completeness before implementation.

Community
Advanced
TravisLeeeeeeTravisLeeeeee
110

Scrum

Transform epics into sprint-ready user stories with acceptance criteria.

Community
Intermediate
nicograefnicograef
2

write-prd

Generate structured product requirements documents through iterative clarification and codebase analysis.

Community
Advanced
zhizhunbaozhizhunbao

dev-scrum

Generate sprint backlogs, user stories, and task breakdowns from PRD requirements.

Community
Advanced