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:
@@ -71,7 +71,17 @@ grep -E "^### Phase [0-9]+" .planning/ROADMAP.md | tail -1
|
||||
|
||||
Next phase starts at: [last_phase + 1]
|
||||
|
||||
**Gather phases (3-6 recommended):**
|
||||
**Check depth setting and gather phases accordingly:**
|
||||
|
||||
```bash
|
||||
cat .planning/config.json 2>/dev/null | grep depth
|
||||
```
|
||||
|
||||
| Depth | Phases/Milestone |
|
||||
|-------|------------------|
|
||||
| Quick | 3-5 |
|
||||
| Standard | 5-8 |
|
||||
| Comprehensive | 8-12 |
|
||||
|
||||
If context from discuss-milestone provided, use that scope.
|
||||
|
||||
@@ -359,7 +369,7 @@ Numbers continue from previous milestone. Names describe content.
|
||||
- Don't restart phase numbering at 01 (continue sequence)
|
||||
- Don't add time estimates
|
||||
- Don't create Gantt charts
|
||||
- Don't plan more than 6 phases per milestone (scope creep)
|
||||
- Respect depth setting for phase count (quick: 3-5, standard: 5-8, comprehensive: 8-12)
|
||||
- Don't modify completed milestone sections
|
||||
|
||||
Milestones are coherent chunks of work, not project management artifacts.
|
||||
@@ -368,7 +378,7 @@ Milestones are coherent chunks of work, not project management artifacts.
|
||||
<success_criteria>
|
||||
Milestone creation is complete when:
|
||||
- [ ] Next phase number calculated correctly (continues from previous)
|
||||
- [ ] 3-6 phases defined with clear names
|
||||
- [ ] Phases defined per depth setting (quick: 3-5, standard: 5-8, comprehensive: 8-12)
|
||||
- [ ] Research flags assigned for each phase
|
||||
- [ ] ROADMAP.md updated with new milestone section
|
||||
- [ ] Phase directories created
|
||||
|
||||
@@ -81,7 +81,35 @@ Select (comma-separate for multiple):
|
||||
</step>
|
||||
|
||||
<step name="identify_phases">
|
||||
Derive phases from the actual work needed. The phase count emerges from the project—don't impose a number.
|
||||
Derive phases from the actual work needed.
|
||||
|
||||
**Check depth setting:**
|
||||
```bash
|
||||
cat .planning/config.json 2>/dev/null | grep depth
|
||||
```
|
||||
|
||||
<depth_guidance>
|
||||
**Phase count targets by depth:**
|
||||
|
||||
| Depth | Target Phases | 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.**
|
||||
|
||||
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
|
||||
- If you're tempted to combine two things, make them separate phases instead
|
||||
|
||||
For quick depth:
|
||||
- Combine related work aggressively
|
||||
- Focus on critical path only
|
||||
- Defer nice-to-haves to future milestones
|
||||
</depth_guidance>
|
||||
|
||||
**Phase Numbering System:**
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user