Task Decomposition

Analyze a task and decompose it into atomic, verifiable sub-tasks when scope exceeds ~100 lines.

When to Use

• Estimated >100 lines of code change
• Multiple unrelated files changing
• Multiple state transitions or new states
• Backend + frontend changes beyond contract sync
• Vague descriptions ("implement pipeline", "add full support")

Process

1. Analyze scope: Read relevant files, estimate lines per area
2. Identify boundaries: Find natural cut points (interfaces, modules, layers)
3. Propose sub-tasks: Create checkbox list with line estimates
4. Return proposal for human confirmation