task-decomposition

Task decomposition breaks large projects into atomic, assignable steps by analyzing goals, identifying phases, mapping dependencies, and assigning work to agents. Start with your main objective and progressively split it into smaller, independent tasks until each is small enough for one person or agent to complete.

Structure your workflow using layered decomposition: define goals, break work by feature and phase, ensure tasks are atomic and independent, map task dependencies, then assign each to specific agents. This approach scales coordination across teams and automation systems.

Atomic tasks have no internal dependencies, can be completed by a single agent, and produce a clear, measurable output. Apply the decomposition framework: if a task requires coordination with another task or multiple people, break it further until each piece stands alone.

Yes. Task decomposition applies directly to feature planning. Split a feature request into research, design, implementation, testing, and documentation phases, then decompose each phase into atomic tasks with explicit dependencies and owner assignments.

Missed dependencies cause scheduling conflicts and bottlenecks—tasks start before their inputs are ready. Map dependencies explicitly as part of decomposition: document which tasks block others, identify parallel work, and validate the sequence before assignment.