task-coordination-strategies

Strategies for decomposing complex tasks into parallelizable units, designing dependency graphs, writing effective task descriptions, and monitoring workload across agent teams. Split work by architectural layer: Best for : Full-stack features, vertical slices Split work by functional component: Best for : Microservices, modular architectures Split work by cross-cutting concern: Best for : Code reviews, audits Split work by file/directory boundaries: Best for : Parallel implementation, conflict avoidance Independent (Best parallelism) : Sequential (Necessary dependencies) : Diamond (Mixed) : Every task should include: - Breaking down a complex task for parallel execution - Designing task dependency relationships (blockedBy/blocks) - Writing task descriptions with clear acceptance criteria - Monitoring and rebalancing workload across teammates - Identifying the critical path in a multi-task workflow - Frontend components - Backend API endpoints - Database migrations/models - Test suites - Authentication module - User profile module - Notification module - Security review - Performance review - Architecture review - src/components/ — Implementer 1 - src/api/ — Implementer 2 - src/utils/ — Implementer 3 - Minimize chain depth — Prefer wide, shallow graphs over deep chains - Identify the critical path — The longest chain determines minimum completion time - Use blockedBy sparingly...