E2e Driven Iteration

Use at the start of every inner-loop iteration where the goal is to fix a bug / close a failing test / reach a green E2E. Forbids editing code without first running the E2E to capture a fresh loss signal, and forbids declaring "done" without the E2E passing. Makes the cycle "E2E → loss → 5-why-by-layer → fix → E2E" the only admissible rhythm.

veegee82 Updated 2 repo stars
Four axes of gradient descent — code (θ), deliverable (y), method (m), reasoning chain (t) — with LDD as the optimizer

File contents

veegee82/loss-driven-development commit 4dae6174e8

Frequently asked questions

npx get-skill add veegee82/e2e-driven-iteration