| name | tier3-decompose |
| description | Break a Tier 3 (🔴) task into 3-5 Tier-2-shaped sub-tasks before editing. Use whenever picked task is Tier 3. |
tier3-decompose
A Tier 3 task is too broad for one diff. Do NOT skip it. Decompose.
Procedure
- Read parent task block from TASK_BOARD.md (Objective + Affected files only).
- Identify natural seams: public symbols, file boundaries, single-concern groups (e.g. key bindings vs rendering).
- Write 3-5 sub-tasks. Each must be:
- One file or one logical group.
- Has its own Validation command (from
validate skill).
- Tier 2 shape: editable in one focused diff.
- Append sub-tasks to TASK_BOARD.md under a new sub-section beneath the parent:
#### T<parent>.a — <sub objective>
- Affected files: ...
- Validation: ...
- Difficulty: 🟡
#### T<parent>.b — ...
- Execute ONLY the first sub-task this turn. Validate. Stop.
Rules
- Never attempt parent + sub in same diff.
- One safe sub-step shipped = successful iteration even if parent unfinished.
- Preserve original import paths via re-exports when moving symbols.
