TDD Enforcement Algorithm FAQs

Question 1

What happens if code was already written without tests?

Accepted Answer

The algorithm mandates a recovery path where any implementation code written without a preceding failing test must be deleted via git reset or rm to ensure no 'sunk cost' exceptions.

Question 2

Why does the algorithm include a self-test section?

Accepted Answer

The self-test ensures the AI agent demonstrates total comprehension of the rules before proceeding, catching potential compliance failures before they enter the codebase.

Question 3

Can I use this for exploratory prototyping?

Accepted Answer

Yes, but only if a 'throwaway prototype exception' is explicitly approved by the user; otherwise, the standard TDD enforcement rules apply.

Question 4

Is this compatible with other testing frameworks?

Accepted Answer

Yes, this algorithm focuses on the 'when' and 'why' of TDD compliance and is designed to work upstream of any specific testing methodology or library.

Question 5

How does this skill differ from standard TDD instructions?

Accepted Answer

While standard instructions use 'must' or 'should,' this skill uses a boolean decision tree that leaves no room for AI interpretation or excuses like 'this code is too simple to test.'

TDD Enforcement Algorithm

Key Features

Use Cases

TDD Enforcement Algorithm

Key Features

Use Cases