work-breakdown-structure

Guide for decomposing projects into Epics, Stories, Features, and Tasks. Use when planning features or capturing work in MCP tools.

⭐23stars🔀25forks📁View on GitHub🕐Updated Jan 8, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill provides a structured framework for Work Breakdown Structure (WBS), allowing users to systematically decompose complex projects into manageable Epics, Stories, Features, and Tasks. It enhances project clarity and execution by establishing standardized hierarchies, naming conventions, and integration patterns specifically optimized for MCP-based task management and software development lifecycles.

Use Cases

  • Decomposing a major product objective into user-facing stories and granular technical components to facilitate accurate sprint planning.
  • Implementing a standardized ID convention (e.g., E-1/S-1/F-1/T-1) to maintain strict traceability between design documentation and active task trackers.
  • Automating the generation of structured task entries for MCP tools, ensuring every work item includes mandatory acceptance criteria and references to technical specifications.
  • Scaling project planning depth based on organization size, from small projects requiring few tasks to enterprise-level initiatives with complex hierarchies.
namework-breakdown-structure
descriptionGuide for decomposing projects into Epics, Stories, Features, and Tasks. Use when planning features or capturing work in MCP tools.

Work Breakdown Structure (WBS)

Hierarchy

Level Purpose Example
Epic Major objective "User Authentication System"
Story User-facing capability "Users can register and login"
Feature Technical component "JWT token management"
Task Atomic unit (1-4 hrs) "Create JWT signing service"

ID Convention

Epic:    E-[n]                    → E-1
Story:   E-[n]/S-[n]              → E-1/S-1
Feature: E-[n]/S-[n]/F-[n]        → E-1/S-1/F-1
Task:    E-[n]/S-[n]/F-[n]/T-[n]  → E-1/S-1/F-1/T-1

Minimum Decomposition by SDLC

Tier Epics Stories Features Tasks
Small 1 2+ 3+ 5+
Medium 2 4+ 8+ 15+
Large 3 8+ 15+ 30+
Enterprise 5 15+ 30+ 60+

MCP Task Format

Pattern: [TYPE] Title | Refs: doc#section | AC: Acceptance criteria

# Epic
mcp__gaia__update_task("E-1", "[EPIC] Auth System | Refs: security.md | AC: All auth flows work", "pending", "Architect")

# Story
mcp__gaia__update_task("E-1/S-1", "[STORY] User login | Refs: api.md#auth | AC: Login/logout E2E", "pending", "Builder")

# Feature
mcp__gaia__update_task("E-1/S-1/F-1", "[FEATURE] JWT tokens | Refs: security.md#jwt | AC: Token refresh works", "pending", "Builder")

# Task
mcp__gaia__update_task("E-1/S-1/F-1/T-1", "[TASK] JWT service | Refs: security.md#jwt | AC: Valid JWTs generated", "pending", "Builder")

Rules

  • Every item MUST reference design docs
  • Every item MUST have testable acceptance criteria
  • Tasks should be 1-4 hours (exceptions: research, debugging)
  • NEVER create TODO.md or markdown task files - use MCP only