decompose

Task decomposition splits complex development work into small, ordered subtasks ranging from 5 to 30 minutes. It maps explicit dependencies between tasks and assigns a clear verification step to each subtask to ensure implementation correctness.

Architecture-aware sequencing orders implementation planning by following system layers. It progresses from core types and business logic through infrastructure, presentation, and tests, ensuring foundational dependencies are resolved before higher-level tasks begin.

Use task decomposition after investigation, design decisions, and approach confirmation are complete. It converts a confirmed development approach into an implementation plan with paired implementation-and-test planning and verification steps.

Dependency mapping identifies which subtasks must be completed first and which can run in parallel. By tracking these dependencies during task decomposition, you ensure that foundational work is finished before dependent tasks start.

Implementation planning applies to core types, business logic, infrastructure, presentation, tests, and cross-cutting checks. Task decomposition ensures each area receives paired implementation-and-test planning with specific verification steps.

The best way to plan verification steps is to pair every implementation task with a corresponding test during task decomposition. This ensures each subtask has a defined validation method confirming completion before moving forward.