task-decomposer

Task decomposition divides large projects into single-purpose subtasks with clear inputs, outputs, and dependencies. Start by assessing complexity and constraints, then systematically split work into half-day to one-day units, ensuring each task has a defined objective and explicit execution order for clarity and automation readiness.

Optimal granularity balances manageability with efficiency. Evaluate task size and dependencies, then adjust by merging overly small tasks or splitting large ones until each unit maps to a single AI workflow or command. Half-day to one-day work items typically achieve the right balance for automation and team coordination.

Workflow mapping requires eliciting goals, constraints, resources, and completion criteria from stakeholders. Assess the workflow's complexity and dependencies, then generate a structured breakdown where each task has one clear objective. Sequence tasks explicitly to show dependencies and ensure downstream processes receive well-defined inputs.

Yes. Task decomposition applies across task collection, complexity assessment, and sequencing for multi-step projects. It identifies bottlenecks, clarifies resource needs, and enables parallel execution by creating discrete, independently manageable units with explicit dependencies and completion criteria.

Collect project goals, constraints, available resources, and completion criteria upfront. These inputs inform complexity assessment and decomposition strategy. Clear requirements ensure the resulting subtasks have well-defined inputs, outputs, and dependencies that map cleanly to automation or team workflows.

Decompose when a task spans multiple days, involves distinct steps, or requires different resources or expertise. Use complexity assessment to determine necessity. Tasks decomposing into clearly separable single-purpose units with independent inputs and outputs benefit most from breakdown; simple, unified tasks may remain whole.