Coding Pipeline

A disciplined 4-phase workflow for any non-trivial coding task. Each phase has a clear purpose, explicit exit criteria, and a loop-back rule when things go wrong. The phases exist because AI agents' default failure mode is blind iteration: edit → build → edit → build → give up. This skill forces hypothesis-driven work, one-fix-at-a-time discipline, root-cause verification, and bounded debugging.

This is a rigid skill — follow the phases exactly. Do not skip, merge, or reorder.

Core Rule

Every non-trivial task — bug fix, feature, refactor — goes through all 4 phases in order: