Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
88
83%
Does it follow best practices?
Impact
96%
1.18xAverage score across 3 eval scenarios
Passed
No findings from the security scan
The canonical home for this skill is tdd in mattpocock/skills
Vertical slice TDD workflow
Test before code per cycle
100%
100%
No horizontal slicing
100%
100%
At least 3 cycles documented
100%
100%
Tracer bullet first
100%
100%
Behavior-named tests
100%
100%
Planning step documented
0%
100%
Single assertion per test
50%
40%
Public interface only in tests
100%
100%
No internal mocking
100%
100%
Minimal code per cycle
100%
100%
Deep module interface design
Small public interface
50%
100%
Functions return values
100%
100%
Tests use public API only
100%
100%
No internal helpers tested
100%
100%
Behavior-named tests
100%
100%
No implementation assertions
100%
100%
Refactor notes present
100%
100%
Tests pass after refactor
30%
40%
Private helpers not re-exported
100%
100%
No side-effect verification
100%
100%
System boundary mocking and dependency injection
Dependency injection for externals
100%
100%
No internal mocking
0%
100%
System boundary mocks only
0%
100%
SDK-style email mock
100%
100%
SDK-style analytics mock
100%
100%
No call count assertions
0%
100%
No call order assertions
100%
100%
Behavior-focused tests
50%
100%
Tests verify return values
100%
100%
No generic fetch mock
100%
100%
f1cbf2f
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.