task-coordination-strategies

1# Task Coordination Strategies
2 
3Strategies for decomposing complex tasks into parallelizable units, designing dependency graphs, writing effective task descriptions, and monitoring workload across agent teams.
4 
5## When to Use This Skill
6 
7- Breaking down a complex task for parallel execution
8- Designing task dependency relationships (blockedBy/blocks)
9- Writing task descriptions with clear acceptance criteria
10- Monitoring and rebalancing workload across teammates
11- Identifying the critical path in a multi-task workflow
12 
13## Task Decomposition Strategies
14 
15### By Layer
16 
17Split work by architectural layer:
18 
19- Frontend components
20- Backend API endpoints
21- Database migrations/models
22- Test suites
23 
24**Best for**: Full-stack features, vertical slices
25 
26### By Component
27 
28Split work by functional component:
29 
30- Authentication module
31- User profile module
32- Notification module
33 
34**Best for**: Microservices, modular architectures
35 
36### By Concern
37 
38Split work by cross-cutting concern:
39 
40- Security review
41- Performance review
42- Architecture review
43 
44**Best for**: Code reviews, audits
45 
46### By File Ownership
47 
48Split work by file/directory boundaries:
49 
50- `src/components/` — Implementer 1
51- `src/api/` — Implementer 2
52- `src/utils/` — Implementer 3
53 
54**Best for**: Parallel implementation, conflict avoidance
55 
56## Dependency Graph Design
57 
58### Principles
59 
601. **Minimize chain depth** — Prefer wide, shallow graphs over deep chains
61…