feat: add depth parameter for planning thoroughness

Adds depth setting (quick/standard/comprehensive) to control how many
phases and plans get created. Tasks per plan stays constant at 2-3.

- Quick: 3-5 phases, 1-3 plans each
- Standard: 5-8 phases, 3-5 plans each
- Comprehensive: 8-12 phases, 5-10 plans each

Depth increases plan COUNT, never plan SIZE. More plans = more
thoroughness with same quality per plan.

Files changed:
- new-project.md: depth question after mode
- config.json: depth field added
- create-roadmap.md: depth-aware phase guidance
- plan-phase.md: depth-aware plan splitting
- scope-estimation.md: depth calibration section
- create-milestone.md: removed hardcoded 3-6 limit
- new-milestone.md: removed hardcoded 3-6 limit
- roadmap.md template: depth-aware guidance

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Lex Christopherson
2026-01-04 18:31:59 -06:00
parent b04034267d
commit 484134e63c
8 changed files with 121 additions and 8 deletions

View File

@@ -226,6 +226,34 @@ See ~/.claude/get-shit-done/references/checkpoints.md for checkpoint structure.
<step name="estimate_scope">
After tasks, assess against quality degradation curve.
**Check depth setting:**
```bash
cat .planning/config.json 2>/dev/null | grep depth
```
<depth_aware_splitting>
**Plan count targets by depth:**
| Depth | 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.**
For comprehensive depth:
- Create MORE plans, 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
- Each plan stays focused: 2-3 tasks, single concern
For quick depth:
- Combine aggressively into fewer plans
- 1-3 plans per phase is fine
- Focus on critical path
</depth_aware_splitting>
**ALWAYS split if:** >3 tasks, multiple subsystems, >5 files in any task, complex domains (auth, payments).
**If scope appropriate (2-3 tasks, single subsystem, <5 files/task):** Proceed to confirm_breakdown.