TDD Enforcement Algorithm

Test-driven development enforcement uses an algorithmic decision tree to mandate writing a failing test before any implementation code. The Skill checks whether a test exists first; if not, it blocks code writing and requires the test to be written immediately, ensuring every feature has prior test coverage.

If code is written without a preceding failing test, the Skill's recovery algorithm mandates deletion of the untested code using git reset --hard or file removal. This prevents technical debt and enforces strict test-first compliance regardless of time pressure or code complexity.

Yes. The Skill provides explicit recovery rules to identify and delete any code written without a preceding failing test. It overrides common rationalizations like "too simple" or "time pressure" to guarantee that only test-backed code remains in the codebase.

The Skill applies deterministic boolean checks with a single execution path: before writing code, it verifies a failing test exists; if absent, code writing stops. If code already exists without tests, the algorithm mandates immediate deletion with no interpretive flexibility or exceptions.

The Skill explicitly invalidates common excuses including "code is too simple," "time pressure," "deadline constraints," and "sunk cost." It enforces algorithmic compliance with no room for rationalization, ensuring robust and well-tested software across all code paths.

Yes. The Skill integrates with Git, using commands like git reset --hard to enforce untested code deletion when recovery is needed. It works within existing Git-based workflows to ensure test-first development at the version control level.