From 9e70b89ca1c2b5c69afd03cdb6b6e1607da92664 Mon Sep 17 00:00:00 2001 From: Lex Christopherson Date: Tue, 13 Jan 2026 17:07:29 -0600 Subject: [PATCH] docs(plan-phase): restore TDD reasoning explanation Restored context-budget reasoning for why TDD features get dedicated plans: - TDD requires 2-3 execution cycles consuming 50-60% context - Test framework setup handled in first TDD plan's RED phase Co-Authored-By: Claude Opus 4.5 --- get-shit-done/workflows/plan-phase.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/get-shit-done/workflows/plan-phase.md b/get-shit-done/workflows/plan-phase.md index bf1f5e3f1..72b663614 100644 --- a/get-shit-done/workflows/plan-phase.md +++ b/get-shit-done/workflows/plan-phase.md @@ -277,6 +277,10 @@ Standard tasks (remain in standard plans): → Yes: Create a dedicated TDD plan for this feature (one feature per TDD plan) → No: Standard task in standard plan +**Why TDD gets its own plan:** TDD requires 2-3 execution cycles (RED → GREEN → REFACTOR), each with file reads, test runs, and potential debugging. Embedded in a multi-task plan, TDD work consumes 50-60% of context alone, degrading quality for remaining tasks. + +**Test framework:** If project has no test setup and TDD plans are needed, the first TDD plan's RED phase handles framework setup as part of writing the first test. + See `~/.claude/get-shit-done/references/tdd.md` for TDD plan structure. **Checkpoints:** Visual/functional verification → checkpoint:human-verify. Implementation choices → checkpoint:decision. Manual action (email, 2FA) → checkpoint:human-action (rare).