# Skill: Task Decomposition

Purpose: Break an approved technical spec into atomic, independently verifiable tasks.

## Steps
1. Read the approved spec's Technical Design section.
2. List tasks in dependency order: schema changes first, then — for each unit of backend logic — a failing-test task followed by an implementation task, then UI, then verification.
3. For any task implementing behavior that can be automated-tested, precede it with a separate task to write a test that fails against the current code (red), and scope the implementation task as "implement until that test passes" (green). Do not combine test-writing and implementation into one task.
4. For legacy stacks without a test harness, precede the implementation task with a task to write the manual verification step it must satisfy, as the TDD-equivalent artifact.
5. Each task should touch the minimum number of files necessary.
6. Each task should have a clear, testable definition of done.
7. Write the checklist directly into the spec's Implementation Plan section.