Task Decomposition
Break down complex tasks into atomic, actionable goals with clear dependencies.
When to Use
- Complex user requests with multiple components
- Multi-phase projects requiring coordination
- Tasks that could benefit from parallel execution
- Planning agent coordination strategies
Decomposition Framework
1. Requirements Analysis
- Primary objective
- Implicit requirements (quality, performance)
- Constraints (time, resources)
- Success criteria
2. Goal Hierarchy
Main Goal
├─ Sub-goal 1
│ ├─ Task 1.1 (atomic)
│ └─ Task 1.2 (atomic)
├─ Sub-goal 2
└─ Sub-goal 3
3. Dependency Types
| Type |
Symbol |
Example |
| Sequential |
A → B → C |
B needs A's output |
| Parallel |
A─┐ B─┐ C─┘ |
Independent, concurrent |
| Converging |
A─┐ B─┼─> D |
D needs A, B, C |
| Resource |
A, B |
Sequential or pooled |
4. Success Criteria
For each task:
- Input: What data/state is needed
- Output: What artifacts will be produced
- Quality: Performance, testing, docs requirements
Decomposition Patterns
| Pattern |
Use Case |
| Layer-Based |
Architectural changes (data, logic, API, test, docs) |
| Feature-Based |
New features (MVP, error handling, optimization, integration) |
| Phase-Based |
Large projects (research, foundation, core, integration, polish) |
| Problem-Solution |
Debugging (reproduce, diagnose, design, fix, verify, prevent) |
Quality Checklist
✓ Atomic and actionable
✓ Dependencies clearly identified
✓ Success criteria measurable
✓ No task too large (>4 hours)
✓ Parallelization opportunities identified
✗ Tasks too large or vague
✗ Missing dependencies
✗ Unclear success criteria
✗ Missing quality/testing tasks
Integration with GOAP
Task decomposition is Phase 1 of GOAP:
- Receive request
- Apply decomposition
- Create execution plan
- Execute with monitoring
- Report results
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: task-decomposition3description: Break down complex tasks into atomic, actionable goals with clear dependencies and success criteria. Use when planning multi-step projects, coordinating agents, or decomposing complex requests. Use when this capability is needed.4---56# Task Decomposition78Break down complex tasks into atomic, actionable goals with clear dependencies.910## When to Use1112- Complex user requests with multiple components13- Multi-phase projects requiring coordination14- Tasks that could benefit from parallel execution15- Planning agent coordination strategies1617## Decomposition Framework1819### 1. Requirements Analysis2021- Primary objective22- Implicit requirements (quality, performance)23- Constraints (time, resources)24- Success criteria2526### 2. Goal Hierarchy2728```29Main Goal30├─ Sub-goal 131│ ├─ Task 1.1 (atomic)32│ └─ Task 1.2 (atomic)33├─ Sub-goal 234└─ Sub-goal 335```3637### 3. Dependency Types3839| Type | Symbol | Example |40|------|--------|---------|41| Sequential | A → B → C | B needs A's output |42| Parallel | A─┐ B─┐ C─┘ | Independent, concurrent |43| Converging | A─┐ B─┼─> D | D needs A, B, C |44| Resource | A, B | Sequential or pooled |4546### 4. Success Criteria4748For each task:49- **Input**: What data/state is needed50- **Output**: What artifacts will be produced51- **Quality**: Performance, testing, docs requirements5253## Decomposition Patterns5455| Pattern | Use Case |56|---------|----------|57| Layer-Based | Architectural changes (data, logic, API, test, docs) |58| Feature-Based | New features (MVP, error handling, optimization, integration) |59| Phase-Based | Large projects (research, foundation, core, integration, polish) |60| Problem-Solution | Debugging (reproduce, diagnose, design, fix, verify, prevent) |6162## Quality Checklist6364✓ Atomic and actionable65✓ Dependencies clearly identified66✓ Success criteria measurable67✓ No task too large (>4 hours)68✓ Parallelization opportunities identified6970✗ Tasks too large or vague71✗ Missing dependencies72✗ Unclear success criteria73✗ Missing quality/testing tasks7475## Integration with GOAP7677Task decomposition is Phase 1 of GOAP:781. Receive request792. Apply decomposition803. Create execution plan814. Execute with monitoring825. Report results8384---85> Converted and distributed by [TomeVault](https://tomevault.io/claim/d-o-hub) — claim your Tome and manage your conversions.86<!-- tomevault:4.0:skill_md:2026-04-13 -->
tomevault-io