| name | task-decomposition |
| description | Convert technical plans into actionable development tasks with dependency graphs, effort estimates, and parallelization opportunities. |
| allowed-tools | Read, Bash, Grep, Glob, Agent, AskUserQuestion |
| graph | {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]} |
- When breaking down a large feature into implementable units
- When identifying parallelization opportunities in a task set
- When estimating effort and critical path for a feature
Key Principle
Every task must trace back to at least one specification requirement. Tasks must be atomic enough for a single development session. Dependency graphs must be acyclic.
Process
- Decompose components - Break architecture components into implementable tasks
- Define tasks - Each with id, title, description, acceptance criteria, dependencies, effort
- Build dependency graph - Show task ordering constraints
- Identify parallel groups - Tasks with no mutual dependencies
- Determine critical path - Longest dependency chain
- Generate test tasks - Testing tasks alongside implementation
- Map to requirements - Traceability from tasks to specification
- Human review - Approve task list before implementation
Tool Use
Invoke via babysitter process: methodologies/spec-kit/spec-kit-planning (task decomposition phase)
Full pipeline: methodologies/spec-kit/spec-kit-orchestrator
