Break epics into parallelizable tasks with acceptance criteria, effort estimates, and dependency graphs.
Scanned 5/29/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill task-decomposition --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Task Decomposition?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-task-decomposition)More formats (shields.io, HTML) on the badges page.
# 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...