breakdown

Name: breakdown
Availability: InStock
Author: GGPrompts

Break down epics and features into backlog tasks with dependencies.

147|10|Updated Nov 17, 2025

Search Tags:#dependencies #sprint planning #task sizing #epic decomposition #break down epics #backlog tasks

Ready to run

npx skills add https://github.com/GGPrompts/TabzChrome --skill breakdown

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: breakdown
Source: https://github.com/GGPrompts/TabzChrome/tree/main/plugins/planner/skills/breakdown
Command: npx skills add https://github.com/GGPrompts/TabzChrome --skill breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams convert large epics and features into concrete, independent backlog tasks with clear dependencies.

Core Features & Use Cases

Structured patterns: Provides New Feature, Refactor, and Bug Fix decomposition patterns to guide task creation.
Dependency sequencing: Defines task order and parallelizable work to optimize sprint planning.
Sizing guidance: Suggests target task sizes (XS–M) to balance workload and delivery risk.

Quick Start

Break down a new feature into a set of subtasks with clear owners, estimates, and dependencies, and align them to an upcoming sprint.

Frequently Asked Questions about breakdown

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

FAQPage Schema

How do I break down epics into actionable backlog tasks for sprint planning?▼

To break down epics into actionable backlog tasks, apply structured decomposition patterns for new features, refactors, and bug fixes to generate concrete subtasks with clear dependencies and sizing guidance.

What is the best way to sequence dependencies when decomposing a large feature?▼

Sequencing dependencies during feature decomposition involves defining task order and identifying parallelizable work to optimize sprint planning and ensure smooth delivery of backlog tasks.

Can I use structured task sizing for backlog items during issue creation?▼

Yes, structured task sizing suggests target sizes from XS to M for backlog items, which helps balance team workload and manage delivery risk during issue creation and sprint scoping.

How does epic decomposition handle different types of work like refactors and bug fixes?▼

Epic decomposition enforces specific patterns for new features, refactors, and bug fixes, ensuring that each work type converts into independent subtasks with appropriate dependency sequencing.

When do I need to decompose features into multiple subtasks for a backlog?▼

You need to decompose features into subtasks when handling large features that require multiple subtasks, ensuring each backlog item is concrete, independent, and ready for sprint planning.