From 35739c84de9e0ebe4adf0f583eac5b33fd17c5b9 Mon Sep 17 00:00:00 2001 From: Lex Christopherson Date: Sun, 4 Jan 2026 20:07:22 -0600 Subject: [PATCH] fix: clarify depth controls compression, not inflation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Depth sets a ceiling on compression, not a floor on expansion. Small phases stay small even in comprehensive mode. - Comprehensive auth = 8 plans (work warrants it) - Comprehensive "add favicon" = 1 plan (that's all it is) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- commands/gsd/new-project.md | 2 +- get-shit-done/references/scope-estimation.md | 13 +++++++++---- get-shit-done/workflows/create-roadmap.md | 13 ++++++++----- get-shit-done/workflows/plan-phase.md | 14 +++++++++----- 4 files changed, 27 insertions(+), 15 deletions(-) diff --git a/commands/gsd/new-project.md b/commands/gsd/new-project.md index 308718a9f..e6bb57287 100644 --- a/commands/gsd/new-project.md +++ b/commands/gsd/new-project.md @@ -245,7 +245,7 @@ Use AskUserQuestion: - "Standard" — Balanced scope and speed (5-8 phases, 3-5 plans each) - "Comprehensive" — Thorough coverage, more phases/plans (8-12 phases, 5-10 plans each) -**Depth controls quantity, not quality.** All depths use 2-3 tasks per plan. Depth determines how many plans get created—more depth means more plans, not bigger plans. +**Depth controls compression tolerance, not artificial inflation.** All depths use 2-3 tasks per plan. Comprehensive means "don't compress complex work"—it doesn't mean "pad simple work to hit a number." Create `.planning/config.json` with chosen mode and depth using `templates/config.json` structure. diff --git a/get-shit-done/references/scope-estimation.md b/get-shit-done/references/scope-estimation.md index 472342fe2..ed3ecb27a 100644 --- a/get-shit-done/references/scope-estimation.md +++ b/get-shit-done/references/scope-estimation.md @@ -103,17 +103,22 @@ Each: 30-40% context, peak quality, focused commits -**Depth controls plan count, not plan size.** +**Depth controls compression tolerance, not artificial inflation.** -| Depth | Phases | Plans/Phase | Tasks/Plan | -|-------|--------|-------------|------------| +| Depth | Typical Phases | Typical Plans/Phase | Tasks/Plan | +|-------|----------------|---------------------|------------| | Quick | 3-5 | 1-3 | 2-3 | | Standard | 5-8 | 3-5 | 2-3 | | Comprehensive | 8-12 | 5-10 | 2-3 | Tasks/plan is CONSTANT at 2-3. The 50% context rule applies universally. -Depth determines thoroughness by creating more phases and more plans—never by cramming more into each plan. +**Key principle:** Derive from actual work. Depth determines how aggressively you combine things, not a target to hit. + +- Comprehensive auth = 8 plans (because auth genuinely has 8 concerns) +- Comprehensive "add favicon" = 1 plan (because that's all it is) + +Don't pad small work to hit a number. Don't compress complex work to look efficient. **Comprehensive depth example:** Auth system at comprehensive depth = 8 plans (not 3 big ones): diff --git a/get-shit-done/workflows/create-roadmap.md b/get-shit-done/workflows/create-roadmap.md index b54ae3cee..d44214f33 100644 --- a/get-shit-done/workflows/create-roadmap.md +++ b/get-shit-done/workflows/create-roadmap.md @@ -89,20 +89,23 @@ cat .planning/config.json 2>/dev/null | grep depth ``` -**Phase count targets by depth:** +**Depth controls compression tolerance, not artificial inflation.** -| Depth | Target Phases | Plans/Phase | Tasks/Plan | -|-------|---------------|-------------|------------| +| Depth | Typical Phases | Typical Plans/Phase | Tasks/Plan | +|-------|----------------|---------------------|------------| | Quick | 3-5 | 1-3 | 2-3 | | Standard | 5-8 | 3-5 | 2-3 | | Comprehensive | 8-12 | 5-10 | 2-3 | -**Tasks/plan is constant (2-3). Depth scales phases and plans, not task density.** +**Key principle:** Derive phases from actual work. Depth determines how aggressively you combine things, not a target to hit. + +- Comprehensive auth system = 8 phases (because auth genuinely has 8 concerns) +- Comprehensive "add favicon" = 1 phase (because that's all it is) For comprehensive depth: - Don't compress multiple features into single phases - Each major capability gets its own phase -- "Too many phases" is NOT a concern—thoroughness is the goal +- Let small things stay small—don't pad to hit a number - If you're tempted to combine two things, make them separate phases instead For quick depth: diff --git a/get-shit-done/workflows/plan-phase.md b/get-shit-done/workflows/plan-phase.md index 9904a53ab..d8de1e93b 100644 --- a/get-shit-done/workflows/plan-phase.md +++ b/get-shit-done/workflows/plan-phase.md @@ -232,20 +232,24 @@ cat .planning/config.json 2>/dev/null | grep depth ``` -**Plan count targets by depth:** +**Depth controls compression tolerance, not artificial inflation.** -| Depth | Plans/Phase | Tasks/Plan | -|-------|-------------|------------| +| Depth | Typical Plans/Phase | Tasks/Plan | +|-------|---------------------|------------| | Quick | 1-3 | 2-3 | | Standard | 3-5 | 2-3 | | Comprehensive | 5-10 | 2-3 | -**Tasks/plan is ALWAYS 2-3. Depth determines how many plans you create, not how big each plan is.** +**Key principle:** Derive plans from actual work. Depth determines how aggressively you combine things, not a target to hit. + +- Comprehensive auth phase = 8 plans (because auth genuinely has 8 concerns) +- Comprehensive "add config file" phase = 1 plan (because that's all it is) For comprehensive depth: -- Create MORE plans, not bigger ones +- Create MORE plans when the work warrants it, not bigger ones - If a phase has 15 tasks, that's 5-8 plans (not 3 plans with 5 tasks each) - Don't compress to look efficient—thoroughness is the goal +- Let small phases stay small—don't pad to hit a number - Each plan stays focused: 2-3 tasks, single concern For quick depth: