test-driven-developmentlisted

# Test-Driven Development > Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference. Rigid, gated process. Follow every gate in order. No skipping. ```dot digraph tdd { rankdir=TB node [shape=box, style="rounded,filled", fillcolor="#f0f0f0"] start [label="Receive test cases\n+ implementation spec", shape=ellipse, fillcolor="#d4edda"] g0 [label="GATE 0\nLoad project context\nFind test conventions", fillcolor="#cce5ff"] g1 [label="GATE 1\nWrite tests from ✅ bullets\nGap scan for edge cases", fillcolor="#cce5ff"] g2 [label="GATE 2\nDelegate to test-runner\nExpect: ALL FAIL", fillcolor="#cce5ff"] tests_pass [label="Tests\nPASS?", shape=diamond, fillcolor="#fff3cd"] stop_investigate [label="STOP\nImplementation exists\nor test is wrong.", shape=ellipse, fillcolor="#f8d7da"] g3 [label="GATE 3\nImplement as described in plan", fillcolor="#cce5ff"] g4 [label="GATE 4\nDelegate to test-runner\nExpect: ALL PASS", fillcolor="#cce5ff"] green_pass [label="Tests\nPASS?", shape=diamond, fillcolor="#fff3cd"] fix_attempt [label="Fix implementation\n(attempt N/3)", fillcolor="#fff3cd"] too_many [label="STOP\nAsk user", shape=ellipse, fillcolor="#f8d7da"] attempts_left [label="Attempts\n< 3?", shape=diamond, fillcolor="#fff3cd"] done [label="Task done ✓", shape=ellipse, fillcolor="#d4edda"] start -> g0 g0 -> g1 g1 -> g2 g2 -> tests_pass tests_pass -> stop_investigate [label