epic-breakdown

Generate user stories, dependencies, and parallelization opportunities from epic specifications.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill epic-breakdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-breakdown
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/epic-breakdown
Command: npx skills add https://github.com/telum-ai/speck --skill epic-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of dissecting large epics into manageable user stories, complete with dependencies and parallelization opportunities, streamlining project planning.

Core Features & Use Cases

  • Automated Story Generation: Extracts user stories from epic specifications and maps them to technical implementations.
  • Dependency Mapping: Identifies and visualizes dependencies between stories.
  • Parallelization Identification: Highlights opportunities for parallel development to speed up delivery.
  • Use Case: A product manager can use this Skill to quickly generate a detailed story breakdown for a new feature epic, ensuring all aspects are considered and dependencies are clear before development begins.

Quick Start

Use the epic-breakdown skill to create a story breakdown for the current epic.

Frequently Asked Questions about epic-breakdown

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

FAQPage Schema
How do I break down an epic into actionable user stories?

To break down an epic into actionable user stories, provide epic and technical specifications. The skill generates a comprehensive story breakdown by mapping user stories to technical implementations and identifying dependencies.

What is dependency mapping in agile project management?

Dependency mapping in agile project management identifies and visualizes relationships between user stories within an epic. It highlights technical requirements and constraints to clarify development sequencing.

How do I identify parallelization opportunities for user stories?

You identify parallelization opportunities by analyzing the generated story breakdown and dependency map. The skill highlights stories without mutual dependencies, allowing concurrent development to speed delivery.

Do I need to provide codebase scans for epic breakdown in a brownfield project?

Codebase scans are optional but recommended for brownfield adaptations. Providing a scan helps the epic breakdown process identify existing code, ensuring technical requirements map accurately to current implementations.

Can I use automated story generation for new feature epics?

Yes, automated story generation extracts user stories from epic specifications and maps them to technical requirements. It is designed for agile workflows to quickly generate detailed story breakdowns for new feature epics.