get-shit-done-cc 1.2.7 → 1.2.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -121,7 +121,7 @@ NEVER include:
121
121
  - Team structures, RACI matrices
122
122
  - Stakeholder management
123
123
  - Sprint ceremonies
124
- - Multi-week estimates
124
+ - Human dev time estimates (hours, days, weeks—Claude works differently)
125
125
  - Change management processes
126
126
  - Documentation for documentation's sake
127
127
 
@@ -142,7 +142,7 @@ Select (comma-separate for multiple):
142
142
  </step>
143
143
 
144
144
  <step name="identify_phases">
145
- Based on the brief/context, identify 3-6 phases.
145
+ Derive phases from the actual work needed. The phase count emerges from the project—don't impose a number.
146
146
 
147
147
  **Incorporate research if available:**
148
148
 
@@ -185,11 +185,20 @@ Use decimal phases (2.1, 2.2) for urgent insertions:
185
185
  **Phase execution order:**
186
186
  Numeric sort: 1 → 1.1 → 1.2 → 2 → 2.1 → 3
187
187
 
188
+ **Deriving phases:**
189
+
190
+ 1. List all distinct systems/features/capabilities required
191
+ 2. Group related work into coherent deliverables
192
+ 3. Each phase should deliver ONE complete, verifiable thing
193
+ 4. If a phase delivers multiple unrelated capabilities: split it
194
+ 5. If a phase can't stand alone as a complete deliverable: merge it
195
+ 6. Order by dependencies
196
+
188
197
  Good phases are:
189
198
 
190
- - **Coherent**: Each delivers something complete
199
+ - **Coherent**: Each delivers one complete, verifiable capability
191
200
  - **Sequential**: Later phases build on earlier
192
- - **Sized right**: 1-3 days of work each (for solo + Claude)
201
+ - **Independent**: Can be verified and committed on its own
193
202
 
194
203
  Common phase patterns:
195
204
 
@@ -511,7 +520,7 @@ Numbers ensure ordering. Names describe content.
511
520
  - Don't create Gantt charts
512
521
  - Don't add resource allocation
513
522
  - Don't include risk matrices
514
- - Don't plan more than 6 phases (scope creep)
523
+ - Don't impose arbitrary phase counts (let the work determine the count)
515
524
 
516
525
  Phases are buckets of work, not project management artifacts.
517
526
  </anti_patterns>
@@ -520,7 +529,7 @@ Phases are buckets of work, not project management artifacts.
520
529
  Roadmap is complete when:
521
530
  - [ ] `.planning/ROADMAP.md` exists
522
531
  - [ ] `.planning/STATE.md` exists (project memory initialized)
523
- - [ ] 3-6 phases defined with clear names
532
+ - [ ] Phases defined with clear names (count derived from work, not imposed)
524
533
  - [ ] **Research flags assigned** (Likely/Unlikely for each phase)
525
534
  - [ ] **Research topics listed** for Likely phases
526
535
  - [ ] Phase directories created
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "get-shit-done-cc",
3
- "version": "1.2.7",
3
+ "version": "1.2.8",
4
4
  "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
5
5
  "bin": {
6
6
  "get-shit-done-cc": "bin/install.js"