eld-sense-task-decomposition

Task decomposition structures a large feature into a three-level hierarchy: a root task, Level 1 major components, and optional Level 2 sub-tasks. This approach clarifies boundaries, enables parallel scheduling, and maps how context flows between levels so implementation stays coordinated.

Context inheritance defines what information, constraints, or dependencies pass from parent tasks to child tasks across decomposition levels. A formal context inheritance map ensures child tasks have the data and constraints they need without duplication, reducing miscommunication and rework.

Use three-level decomposition for complex features, system design projects, and multi-phase workflows where clear modularization, explicit dependencies, and parallel execution matter. It's essential when you need single-responsibility tasks, deterministic planning, and formal tracking of context flow.

Yes. Decomposing tasks into independent Level 1 and Level 2 components with explicit boundaries identifies which work can run in parallel. The context inheritance map shows which tasks depend on shared context, letting you schedule non-blocking work concurrently.

You receive a nested task structure (root, Level 1 components, Level 2 sub-tasks) plus a context inheritance map showing how data and constraints flow between levels. This output guides implementation, dependency tracking, and execution sequencing for complex projects.

Yes. Task decomposition applies to any complex feature with distinct phases or components—like payment processing modules. It breaks the feature into major components and sub-tasks, defines clear boundaries, and maps context flow so each phase knows its inputs and constraints.