From a1f6e9f1dfbe43be2449304405b5a0e4c5b5f118 Mon Sep 17 00:00:00 2001 From: Lex Christopherson Date: Mon, 12 Jan 2026 14:21:13 -0600 Subject: [PATCH] feat(11-04): add parallel-aware splitting strategy to scope-estimation.md - Add philosophy_shift table comparing sequential vs parallel approaches - Add vertical_slice_example showing sequential chains vs parallel independence - Add when_to_restructure guidance for choosing approach - Add file_ownership section for conflict prevention - Add summary_references guidance for minimizing unnecessary deps --- get-shit-done/references/scope-estimation.md | 88 ++++++++++++++++++++ 1 file changed, 88 insertions(+) diff --git a/get-shit-done/references/scope-estimation.md b/get-shit-done/references/scope-estimation.md index de223ab03..15e167f59 100644 --- a/get-shit-done/references/scope-estimation.md +++ b/get-shit-done/references/scope-estimation.md @@ -87,6 +87,94 @@ See `~/.claude/get-shit-done/references/tdd.md` for TDD plan structure. **By verification:** Deploy → 01: Vercel setup (checkpoint), 02: Env config (auto), 03: CI/CD (checkpoint) + +**When parallelization is enabled, optimize for plan independence.** + + +| Aspect | Sequential Planning | Parallel-Aware Planning | +|--------|---------------------|------------------------| +| Grouping | By workflow stage | By vertical slice | +| Dependencies | Implicit (later plans reference earlier) | Explicit (only when genuinely needed) | +| File ownership | Overlap acceptable | Exclusive where possible | +| SUMMARY refs | Chain pattern (02 refs 01, 03 refs 02) | Minimal (only for real data deps) | +| Wave result | Most plans in Wave 2+ | More plans in Wave 1 | + + + +**Sequential (creates chain):** +``` +Plan 01: Create User model, Product model, Order model +Plan 02: Create /api/users, /api/products, /api/orders +Plan 03: Create UserList UI, ProductList UI, OrderList UI +``` +Result: 02 depends on 01 (needs models), 03 depends on 02 (needs APIs) +Waves: [01] → [02] → [03] (fully sequential) + +**Parallel-aware (creates independence):** +``` +Plan 01: User feature (model + API + UI) +Plan 02: Product feature (model + API + UI) +Plan 03: Order feature (model + API + UI) +``` +Result: Each plan self-contained, no file overlap +Waves: [01, 02, 03] (all parallel) + + + +**Restructure for vertical slices when:** +- Phase has 3+ features that are independent +- No shared infrastructure requirements +- Each feature touches different files +- Features can be tested independently + +**Keep sequential when:** +- Genuine data dependencies (Order needs User type) +- Shared foundation required (auth setup before protected features) +- Single feature being built incrementally +- Phase is already a vertical slice + + + +**Explicit file ownership prevents conflicts:** + +```yaml +# Plan 01 frontmatter +files_exclusive: [src/models/user.ts, src/api/users.ts, src/components/UserList.tsx] + +# Plan 02 frontmatter +files_exclusive: [src/models/product.ts, src/api/products.ts, src/components/ProductList.tsx] +``` + +**If file appears in multiple plans:** Later plan depends on earlier (by plan number). +**If file cannot be split:** Plans must be sequential for that file. + + + +**Minimize SUMMARY references when parallel-aware:** + +**Before (sequential habit):** +```markdown + +@.planning/phases/05-features/05-01-SUMMARY.md # Always reference prior +@.planning/phases/05-features/05-02-SUMMARY.md # Chain continues + +``` + +**After (parallel-aware):** +```markdown + +# Only reference if this plan ACTUALLY needs decisions from prior plan +# Most parallel plans don't need any SUMMARY references + +``` + +**Include SUMMARY only when:** +- Prior plan made a decision that affects this plan's approach +- Prior plan created types/interfaces this plan imports +- Prior plan's output is input to this plan + + + **Bad - Comprehensive plan:** ```