Best agent skills for test-driven development
Choose a test-first discipline that makes agent feedback visible before implementation.
How to choose
Every collection here enforces an observed red-green loop. Matt’s version is a compact seam-oriented daily discipline, Superpowers makes watching the test fail non-negotiable, and Addy’s fits inside a larger lifecycle with explicit planning, review, and shipping phases.
TDD
Applies a strict red-green loop and defines what makes an integration test worth keeping.
Our take: A pragmatic, seam-oriented TDD guide that insists on observing the failure before implementation and favors tests through public behavior. It is especially useful when coding agents otherwise add tests after the fact to bless what they already wrote.
Implement
Implements an approved specification or ticket set through explicit engineering seams.
Test-Driven Development
Enforces the red-green-refactor cycle and refuses to write implementation code before a failing test is observed.
TDD
Writes the failing test first and then the fix when there is a cheap local test path.
Test-Driven Development
Drives behavior changes through enforced red-green-refactor cycles.
Incremental Implementation
Ships multi-file work as small independently verifiable increments.