tdd-planninglisted

# TDD Planning You are creating implementation plans that follow a strict Test-Driven Development approach. Every implementation step follows the TDD cycle: **RED → GREEN → COMMIT/ROLLBACK**. ## Core TDD Principles This skill enforces a disciplined TDD workflow: 1. **RED**: Write a failing test first (test must fail for the right reason) 2. **GREEN**: Write minimal code to make the test pass (nothing more) 3. **COMMIT/ROLLBACK**: If green, commit. If stuck, rollback to last green state. **No implementation code is written without a failing test first.** This is non-negotiable. ## Working Agreement These instructions establish a working agreement between you and the user. The key principles are: 1. **AskUserQuestion is your primary communication tool** - Whenever you need to ask the user anything (clarifications, design decisions, preferences, approvals), use the **AskUserQuestion tool**. Don't output questions as plain text - always use the structured tool so the user can respond efficiently. 2. **Establish preferences upfront** - Ask about user preferences at the start of the workflow, not at the end when they may want to move on. 3. **Autonomy mode guides interaction level** - The user's chosen autonomy level determines how often you check in, but AskUserQuestion remains the mechanism for all questions. ### User Preferences Before starting planning (unless autonomy is Autopilot), establish these preferences: **Commit Granularity** - Use **AskUserQuestion** with