stepwise-task-execution

# Stepwise Task Execution ## Overview An implementation task is never done in one big move. You understand the task completely, break it into an ordered list of small steps, and drive each step through its own test-and-commit cycle. This is the master workflow every developer role follows on every task; the individual disciplines it orchestrates live in their own skills. **Core principle:** Small, verified, committed steps beat one large uncommitted change every time — for correctness, for review, and for cheap revisions. **REQUIRED SUB-SKILLS:** tdd-workflow (each step is test-first), incremental-commits (commit each green step), verify-before-done (prove it works before handoff), root-cause-debugging (when a step or a revision fails). ## When to Use Every task that changes product code — features, bug fixes, refactors, revisions. Never skip the decomposition because a task "looks small": unexamined small tasks are where scope and edge cases hide. ```dot digraph stepwise { "Task picked up" [shape=box]; "Requirements clear?" [shape=diamond]; "Ask numbered questions\n(add_task_comment)" [shape=box]; "Decompose into steps" [shape=box]; "Execute one step\n(test -> code -> verify -> commit)" [shape=box]; "More steps?" [shape=diamond]; "Verify whole task\n+ every AC" [shape=box]; "Handoff to code_review" [shape=doublecircle]; "Task picked up" -> "Requirements clear?"; "Requirements clear?" -> "Ask numbered questions\n(add_task_commen...