Iteratively refine development plans using TDD methodology. Ensures plans are clear, actionable, and include red-green-refactor cycles with proper test coverage.
Good plans eliminate ambiguity through clear requirements, break work into clear phases, and always include refactoring to capture implementation insights.
When to Use This Skill
Symptom
Example
Unclear acceptance criteria
No definition of "done"
Vague implementation
Missing concrete steps or file changes
Missing/undefined tests
Tests mentioned only as afterthought
Absent refactor phase
No plan to improve code after it works
Ambiguous requirements
Multiple interpretations possible
Missing verification
No way to confirm the change works
Planning Principles
Verwandte Skills
1. Plans Must Be Actionable and Unambiguous
Every step should be concrete enough that another agent could execute it without guessing.
❌ "Improve error handling" → ✓ "Add try-catch to API calls in user-service.ts, return 400 with error message"
❌ "Update tests" → ✓ "Add test case to auth.test.ts: 'should reject expired tokens with 401'"
NEVER include thinking output or other stream-of-consciousness prose mid-plan.
2. Push Back on Unclear Requirements
When requirements are ambiguous, ask questions before proceeding.
3. Tests Define Requirements
Writing test cases forces disambiguation. Use test definition as a requirements clarification tool.
4. TDD is Non-Negotiable
All plans follow: Red → Green → Refactor. The refactor phase is MANDATORY.
The TDD Workflow
Red Phase: Write Failing Tests First
Purpose: Define success criteria through concrete test cases.