tdd-identify

One-line summary

Diagnose which TDD technique fits the current moment — the right Beck move depends on whether you know what to type, whether the test is too big, whether the dependency is too slow, or whether you've just found a bug.

When to use this skill

• A test is red and you're not sure how to make it green.
• You can see the implementation but unsure whether to type it directly or fake-then-generalize.
• You're staring at the next test and can't decide which one to write.
• A test is hitting a slow / external dependency and you're not sure how to isolate.
• You just fixed a bug and aren't sure what kind of test to leave behind.

When NOT to use this skill

• You haven't decided whether to use TDD at all → that's the workflow question, see tdd-red-green-refactor (and Superpowers' test-driven-development if installed).
• You know exactly which technique to apply → go directly to that skill.
• Domain-modeling question that's masquerading as a TDD question → route to ddd-design.

Core content