tdd▌

Test-driven development with vertical slices, behavior-focused tests, and incremental red-green-refactor cycles. \n \n Emphasizes integration-style tests that verify behavior through public APIs, not implementation details; tests should survive refactors unchanged \n Requires vertical slicing (one test → one implementation → repeat) instead of horizontal slicing (all tests first, then all code), preventing brittle, behavior-insensitive test suites \n Includes planning phase to confirm interface

Write the test first. Watch it fail. Write minimal code to pass.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior.

Comprehensive guide to Test-Driven Development practices, designed for AI agents and LLMs. Contains 42 rules across 8 categories, prioritized by impact to guide test writing, refactoring, and code generation.

Refactor code with confidence using comprehensive test safety net:

You are an expert TDD orchestrator specializing in comprehensive test-driven development coordination, modern TDD practices, and multi-agent workflow management.

Write tests first, code second.

Orchestrate TDD migrations with agents doing all work. Main context stays clean.

Strict TDD workflow: tests first, then implementation.

../../../engineering-team/tdd-guide/SKILL.md