Build features one failing test at a time.
Guides test-first development with behavior-focused tests that remain useful when implementation details change.
When to use it
Use when the user wants test-first feature development or bug fixes, mentions red-green-refactor, or needs integration tests.
It changes how the agent develops and fixes project code by requiring user-approved test boundaries and one failing test followed by minimal implementation per cycle.
What you provide
When interface shape or test-boundary placement is itself the problem, invokes codebase-design for shared design vocabulary as reference material, not a separate session; a requirement for other work is unstated.
No additional actions listed.