Tdd

This enforces proper red-green-refactor discipline by requiring a failing test before any implementation. It walks you through understanding the behavior, writing the smallest test that fails for the right reason, making it pass with minimal code, then cleaning up. The workflow explicitly stops you from jumping straight to implementation, which is the usual TDD pitfall. It knows when to ask for clarification versus making low-risk assumptions, prefers testing at real boundaries over mocks, and skips the ceremony for non-behavioral work like formatting. Good for feature work and bug fixes where you can describe the desired outcome in a test first.