tdd-with-llm-agentslisted

# Test-Driven Development with LLM Agents ## Session start Run the full test suite before any new work. Report the baseline (total tests, pass/fail counts). If any tests fail, fix those first. ## Workflow: red/green/refactor Execute one cycle at a time. Never batch. ### RED — write one failing test 1. Write exactly **one** test for the next behavior. 2. Use a descriptive, behavior-focused name (`should reject emails without @ symbol`, not `test case 3`). 3. Follow AAA: Arrange, Act, Assert. 4. Run the test. **Confirm it fails.** If it passes, the test is wrong — it is not exercising new behavior. 5. Do NOT write any implementation code in this phase. ### GREEN — minimal implementation 1. Write the **minimum** code to make the failing test pass. 2. Do NOT modify, delete, or skip any test. Test files are read-only. 3. Do NOT add functionality beyond what the current test requires. 4. Run **all** tests. All must pass. 5. If a previously passing test breaks, fix the implementation — never the test. ### REFACTOR — clean up under green 1. Improve structure: remove duplication, improve naming, simplify logic. 2. Do NOT add new behavior. 3. Run tests after every change. All must stay green. 4. Refactor implementation first (tests are the fixed reference), then optionally refactor tests (implementation is the fixed reference). Never both simultaneously. ### Repeat Return to RED with the next behavior. Continue until the feature is complete. ## Hard constraints