Terminal
Terminal/Skill
Traces the cause of a bug or failing test, then records it in your spec as a new invariant so the bug can't come back.
By Julius Brussee
Works with
npx skills add juliusbrussee/cavekit --skill backpropPlan-then-execute fixes the code & forgets. SDD fixes the code AND edits spec so recurrence is impossible. That edit is backprop.
/build verification./check flags VIOLATE with root cause found.Read failure output / bug report. Find exact file:line of wrong behavior. Name root cause in one caveman sentence.
Ask three questions:
Draft the spec change. Never skip §B; §V/§I/§T are case-by-case.
Template:
§B row: B<next>|<date>|<root cause>|V<N>
§V line: V<next>: <testable rule that would have caught it>
Example:
§B row: B3|2026-04-20|refund job ran twice on retry|V7
§V line: V7: ∀ refund → idempotency key check before charge reversal
New invariant without test = lie. Add failing test first.
Name test so it cites the invariant: TestV7_RefundIdempotent.
Fix code. Run test. Must pass. Run full suite. Must not regress.
Commit spec edit + test + code fix together.
Commit msg: backprop §B.<n> + §V.<N>: <one-line cause>.
! hold over ⊥ forbid).Bad: V8: code should be correct. Good: V8: ∀ pg_query ! params interpolated via driver, ⊥ string concat.
i++ vs i-- in throwaway).Still append §B entry — record that this failure mode was considered. Future bug with same smell → §B search shows precedent.
Every backprop run produces:
No dashboards. No log files. SPEC.md + git is the full history.