tdd-plannerlisted

# TDD Planner Generate high-quality, structured development plans following Test-Driven Development principles for use with the dev-loop command. ## Quality Standard Every plan must meet this checklist before saving: - [ ] Context lists **specific items** to work on (not just "the feature") - [ ] Success criteria are **measurable** (numbers, specific behaviors) - [ ] **Every task** has a file path - [ ] **Code snippets** show implementation structure - [ ] Verification has **expected output** (PASS/FAIL + why) - [ ] Self-correction is **phase-specific**, not generic - [ ] **Files to Modify** table exists - [ ] **New Files to Create** table exists - [ ] Stuck handling is **framework/task-specific** **Reference:** See `references/good-example.md` for expected quality. ## Activation Triggers This skill activates when: - Planning a feature for iterative development - Preparing prompts for dev-loop execution - Breaking down complex tasks into TDD phases - Creating structured development workflows ## Core Principles 1. **Specificity Over Vagueness** - File paths, code snippets, measurable outcomes 2. **Iteration Over Perfection** - Expect multiple passes, not first-draft solutions 3. **Failures as Data** - Red phase tests MUST fail first 4. **Framework Awareness** - Use correct patterns for detected framework ## Required Plan Sections ### 1. Context ```markdown ## Context - **Framework**: Flutter / Django / Next.js / etc. - **Current State**: What exists now - **Test C