task-decomposition
Task Decomposition breaks down epics into 4-5 parallel work streams, creating concrete tasks with Given/When/Then acceptance criteria, effort estimates (S/M/L/XL), and dependency graphs. Use this skill when you need to translate a high-level epic into executable, parallelizable work items that maintain traceability to product requirements and coordinate across multiple development streams.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/task-decomposition && cp -r /tmp/task-decomposition/library/methodologies/ccpm/skills/task-decomposition ~/.claude/skills/task-decompositionSKILL.md
# Task Decomposition Break epics into parallelizable tasks with acceptance criteria, effort estimates, and dependency graphs. ## Agent Task Analyst - `task-analyst` ## Workflow 1. Analyze epic and identify 4-5 parallel work streams 2. Decompose each stream into concrete tasks (parallel) 3. Set acceptance criteria in Given/When/Then format 4. Estimate effort (S/M/L/XL) and set parallelization flags 5. Build cross-stream dependency graph 6. Validate coverage against PRD user stories 7. Fill gaps with additional tasks if needed 8. Write task files to .claude/epics/<featureName>/<N>.md ## Inputs - `projectName` - Project name - `featureName` - Feature identifier - `epic` - Epic from Phase 2 - `prd` - PRD from Phase 1 - `parallelAgents` - Max parallel agents (default: 5) ## Outputs - Task list with acceptance criteria and effort estimates - Work stream definitions - Dependency graph with execution waves - Coverage report with PRD traceability ## Process Files - `ccpm-task-decomposition.js` - Standalone decomposition - `ccpm-orchestrator.js` - Phase 3 of full lifecycle
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement