Root Cause By Layer

Use when encountering a bug, failing test, or unexpected behavior — especially under time pressure where try/except, retry loops, xfail, type-tolerance shims, "I'll clean up later," or compat-for-both-shapes feel like the fastest path. Forbids symptom patches until structural and conceptual origins are named.

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 f91995e01f

Frequently asked questions

npx get-skill add veegee82/root-cause-by-layer