tddlisted

# /aiagentminder:tdd - Test-Driven Development Guided TDD workflow for implementing features through red-green-refactor cycles. This is the full methodology behind `code-quality.md`'s one-liner: "Write a failing test first. Implement the minimal solution. Refactor after green." **Core principle:** Tests verify behavior through public interfaces, not implementation details. A good test survives internal refactors because it doesn't care about internal structure. --- ## Step 0: Read Context Read `.claude/rules/code-quality.md` if it exists — this skill complements that rule with the full structured methodology. Also read `docs/strategy-roadmap.md` for scope context and any testing strategy notes. --- ## Step 1: Planning Before writing any code: 1. **Read existing tests** in the project to learn the test framework, naming conventions, file organization, and assertion style. Match the project's patterns. 2. **Identify the public interface** — what functions, endpoints, or APIs will callers use? Aim for a small interface with deep implementation (fewer methods, simpler parameters, complexity hidden inside). 3. **List 3-7 behaviors to test** — describe what the system does, not how. Each behavior should be observable through the public interface. - Good: "returns 404 when user not found" - Bad: "calls findById with the user ID" 4. **Design for testability** — accept dependencies as parameters instead of creating them internally. Return results instead of producing s