tdd-guidelines

What problem does it solve?

It enforces a strict, evidence-driven test-driven workflow that makes failing tests the starting point and treats passing results as downstream confirmation, preventing premature changes.

Core Features & Use Cases

• Require writing failing tests before implementing the behavior.
• Ensure the test suite captures regressions and guides incremental development.
• Split unrelated changes and run targeted tests to maintain isolation.
• Provide guidance for cross-boundary testing and plan-and-scratchpad workflows.

Quick Start

Plan your task with PLAN.md, write a failing test first, observe red, implement the minimal change, and verify green.