Test-Driven Development (TDD) Workflow FAQs

Question 1

How does this skill handle refactoring?

Accepted Answer

Refactoring is a dedicated step in the workflow that occurs only after a test passes (Green phase). It allows for cleaning up duplication and improving names while the agent ensures that the tests stay green.

Question 2

What if my test passes immediately in the Red phase?

Accepted Answer

If a test passes during the Red phase, it indicates you are either testing existing behavior or the test is flawed. The skill will guide you to fix the test so it fails for the correct reason before proceeding.

Question 3

Does this skill work for bug fixes?

Accepted Answer

Yes, it is excellent for bug fixes. It requires you to write a test that fails by reproducing the bug, ensuring that the subsequent code change actually addresses the reported issue.

Question 4

What is the 'Iron Law' in this TDD skill?

Accepted Answer

The Iron Law dictates that no production code is written without a failing test first. If implementation code is written before the test, the skill encourages deleting it and starting over to ensure the test truly verifies the logic.

Question 5

When should I avoid using the TDD skill?

Accepted Answer

TDD is highly recommended for features and bug fixes but may be overkill for throwaway prototypes, exploratory coding, or simple configuration files where the testing overhead isn't justified.

Test-Driven Development (TDD) Workflow

Key Features

Use Cases

Test-Driven Development (TDD) Workflow

Key Features

Use Cases