Featured dimension
TDD enforcement
Only 49 of 654 frameworks enforce TDD as mandatory — 7%. The community is far more comfortable talking about TDD than enforcing it. But enforcement is migrating progressively from prompt-based suggestion toward structural guarantees: SKILL.md iron-laws with rationalization tables (superpowers), hook-triggered test runners (micro-agent, tdd-guard), and the logical endpoint — compiled Go invariants that cannot be argued with (Liza). This spectrum shows where each framework sits.
185 frameworks have TDD enforced or optional · 49 mandatory · 468 none/unknown
The framework's system prompt or persona explicitly asks the agent to follow TDD. No structural enforcement — just a request.
The workflow requires writing tests before any implementation begins. Enforced by phase structure rather than a compile-time check.
A PostToolUse or Stop hook actually runs the test suite and can block progress if tests fail. Structural enforcement, not prompt-based.
TDD is written as an iron law with pre-built rationalization tables in SKILL.md — the agent is told it can never deviate, with specific countermeasures for the most common attempts to skip it.
TDD enforced (mechanism not specified)
Frameworks where tdd_enforced=yes but the mechanism type wasn't recorded.