| name | task-decomposition |
| description | Break down complex tasks into atomic, actionable goals with clear dependencies. Use when planning work, breaking down features, or organizing tasks. Triggers: "decompose", "break down", "task", "plan", "subtask".
|
| category | meta |
Skill: task-decomposition
Decomposition Rules
- One file per task — each task touches minimal files
- Testable — each task has a clear "done" condition
- Independent — tasks can be done in order with minimal blocking
- Scoped — each task fits in one session
Task Format
## Task N: <title>
**Files:** `<file1>`, `<file2>`
**Tests:** `<test-file>`
**Done:** <clear condition>
**Blocked by:** Task M (if any)
When to Decompose
- Feature has 3+ files to change
- Task spans multiple concerns (UI + logic + tests)
- Estimated time > 30 minutes
Commands
find src/ examples/ -name '*.js' -o -name '*.ts' | xargs wc -l | sort -rn | head -10
find src/ -name '*.js' | wc -l
Rules
- Never create a task that touches more than 3 files
- Each task must have a testable "done" condition
- Block dependencies explicitly in the task format
- Keep tasks small enough to complete in one session
