coordinating-as-kusanagi

Task breakdown transforms a high-level strategy into discrete, sequenced work units. Identify dependencies between tasks, determine which can run in parallel, and create a staged execution plan. This approach clarifies workload distribution and prevents bottlenecks before work begins.

Dependency analysis maps which tasks block others and which can execute simultaneously. By identifying critical paths and independent work streams, you can schedule parallel execution where possible and staged execution where tasks are sequenced. This maximizes team throughput.

Task coordination establishes a clear handoff protocol: decompose work into independent units, assign ownership with explicit task scope, and communicate worktree details and dependencies to each team member. This ensures aligned execution without overlap or gaps.

Yes. Task coordination operates at the planning and delegation layer without modifying code or activating developer tools. It enforces governance by keeping strategy, decomposition, and scheduling separate from implementation execution.

After generating the task plan, hand off explicit worktree assignments and dependency information to developers. Monitor execution progress, surface blockers, and adjust scheduling if dependencies resolve earlier or later than projected.