---

name: work-breakdown-structure description: Guide for decomposing projects into Epics, Stories, Features, and Tasks. Use when planning features or capturing work in MCP tools.

Work Breakdown Structure (WBS)

Hierarchy

ID Convention

CopyEpic:    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

MCP Task Format

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

Copy# 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