task-decomposition

Task decomposition breaks large projects into atomic, actionable sub-tasks with clear dependencies and success criteria. Start by defining your main goal, then systematically divide it into smaller components, mapping sequential and parallel work streams, and establishing testable outputs for each task.

Dependency mapping identifies which tasks must complete before others can start (sequential), which can run simultaneously (parallel), and where multiple streams converge. This prevents bottlenecks and ensures coordinated execution across teams or agents working on different phases.

Success criteria specify inputs, outputs, quality standards, and testing requirements for each atomic task. Clear criteria eliminate ambiguity, enable objective completion verification, and help coordinate handoffs between tasks and team members across multi-phase projects.

Yes. Decomposition creates explicit task hierarchies and dependency maps that clarify ownership, sequence, and integration points. This structure enables parallel work by different agents or teams while maintaining alignment on shared goals and prerequisites.

Use decomposition for multi-phase projects, cross-functional coordination, or complex user requests where hidden dependencies cause rework. It becomes essential when multiple parties need to work independently without constant communication, or when testing and documentation requirements are strict.