epic-breakdown-advisor

Guide product managers through splitting epics into user stories using nine sequential patterns.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/MMXC/openclaw-back --skill epic-breakdown-advisor-mmxc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-breakdown-advisor
Source: https://github.com/MMXC/openclaw-back/tree/main/pm-skills/skills/epic-breakdown-advisor
Command: npx skills add https://github.com/MMXC/openclaw-back --skill epic-breakdown-advisor-mmxc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product managers systematically break down large epics into smaller, manageable user stories using a proven methodology, ensuring vertical slicing and preserving user value.

Core Features & Use Cases

  • Methodical Splitting: Guides users through 9 sequential splitting patterns (Workflow Steps, CRUD, Business Rules, etc.).
  • INVEST Validation: Ensures stories meet quality criteria before and after splitting.
  • Waste Identification: Helps expose and eliminate low-value work.
  • Use Case: A PM has a large "User Profile Management" epic. This Skill helps them break it down into individual stories like "Create User Profile," "View User Profile," "Edit User Profile," and "Delete User Profile," ensuring each delivers value.

Quick Start

Use the epic-breakdown-advisor skill to break down the epic titled "Implement new dashboard widgets".

Frequently Asked Questions about epic-breakdown-advisor

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

FAQPage Schema
How do I break down large epics into actionable user stories?

To break down large epics into actionable user stories, apply Richard Lawrence's 9 sequential splitting patterns sequentially. This method ensures vertical slicing and identifies low-value work before validating the resulting stories using INVEST criteria.

What is the best way to split agile epics while preserving user value?

The best way to split agile epics while preserving user value is to apply vertical slicing through a structured methodology. Sequentially applying 9 splitting patterns like Workflow Steps and CRUD exposes low-value work and maintains end-to-end value delivery.

How does the INVEST validation check work for user stories?

INVEST validation checks that user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. This methodology applies INVEST validation before and after splitting epics to ensure each story meets quality criteria and delivers user value.

When do I need to use story splitting patterns for product management?

You need to use story splitting patterns for product management when you have a large epic that must be broken down into smaller, manageable user stories. This is required when a single epic is too broad for actionable development and needs structured vertical slicing.

Can I eliminate low-value work during epic breakdown?

You can eliminate low-value work during epic breakdown by sequentially applying 9 splitting patterns based on Richard Lawrence's Humanizing Work methodology. This structured approach proactively exposes and removes unnecessary tasks before finalizing user stories.