Stats
Actions
Available In
Tags
Plugin
traced-tdd
A TDD discipline where every test failure traces back to one owning layer. Tests follow the architecture's dependency graph; each layer owns a typed error contract; trust compounds upward.
README
Traced TDD
Every failure traces to one layer. Tests follow the dependency graph. Each layer owns a typed error contract. Trust compounds upward. Ripples stop where you Resolve.
A Claude Code skill that turns the test suite into a diagnostic instrument: when production fails, the error type at the top boundary names the layer where handling broke.
Install
/plugin marketplace add lagz0ne/traced-tdd
/plugin install traced-tdd@traced-tdd-marketplace
What it does
Before writing tests, Claude follows this workflow:
- Draw the layer graph (it's also the test ownership graph).
- Declare a typed error set per layer.
- Build an acknowledgment table — for each error, decide Resolve, Transform, or Propagate.
- Place one test per acknowledgment in its owning layer.
- Verify mechanically.
See SKILL.md for the six rules and diagnostic checklist, and golden-example.md for a worked example on a five-layer registration flow.
License
Stats
Version0.1.0
Stars0
MaintenanceGood
LicenseMIT
Last Commit
Added
Available In
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
