get-shit-done-cc 1.5.29 → 1.6.0

package/README.md

@@ -374,8 +374,7 @@ You're never locked in. The system adapts.
 
 | Command | What it does |
 |---------|--------------|
-| `/gsd:new-milestone [name]` | Start next milestone |
-| `/gsd:discuss-milestone` | Gather context for next milestone |
+| `/gsd:new-milestone [name]` | Start next milestone (questioning → research → requirements → roadmap) |
 
 ### Session
 

package/agents/gsd-project-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-project-researcher
-description: Researches domain ecosystem before roadmap creation. Produces multiple files in .planning/research/ consumed by /gsd:create-roadmap. Spawned by /gsd:research-project orchestrator.
+description: Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*
 color: cyan
 ---
@@ -10,9 +10,10 @@ You are a GSD project researcher. You research the domain ecosystem before roadm
 
 You are spawned by:
 
-- `/gsd:research-project` orchestrator (project-wide research before roadmap)
+- `/gsd:new-project` orchestrator (Phase 6: Research)
+- `/gsd:new-milestone` orchestrator (Phase 6: Research)
 
-Your job: Answer "What does this domain ecosystem look like?" Produce multiple research files that inform roadmap creation.
+Your job: Answer "What does this domain ecosystem look like?" Produce research files that inform roadmap creation.
 
 **Core responsibilities:**
 - Survey the domain ecosystem broadly
@@ -25,7 +26,7 @@ Your job: Answer "What does this domain ecosystem look like?" Produce multiple r
 </role>
 
 <downstream_consumer>
-Your research files are consumed by `/gsd:create-roadmap` which uses them to:
+Your research files are consumed during roadmap creation:
 
 | File | How Roadmap Uses It |
 |------|---------------------|
@@ -807,7 +808,7 @@ When research finishes successfully:
 
 ### Ready for Roadmap
 
-Research complete. Run `/gsd:create-roadmap` to create phase structure.
+Research complete. Proceeding to roadmap creation.
 ```
 
 ## Research Blocked

package/agents/gsd-roadmapper.md

@@ -286,114 +286,23 @@ After roadmap creation, REQUIREMENTS.md gets updated with phase mappings:
 
 ## ROADMAP.md Structure
 
-```markdown
-# Roadmap
-
-**Project:** [name]
-**Created:** [date]
-**Phases:** [N]
-
-## Overview
-
-[2-3 sentences describing the roadmap approach]
-
-## Phases
-
-### Phase 1: [Name]
-
-**Goal:** [What this phase delivers - outcome, not task]
-**Depends on:** Nothing (first phase)
-**Requirements:** [REQ-IDs]
-
-**Success Criteria:**
-1. [Observable user behavior]
-2. [Observable user behavior]
-3. [Observable user behavior]
-
-**Plans:** (created by /gsd:plan-phase)
-
----
-
-### Phase 2: [Name]
-
-**Goal:** [Outcome]
-**Depends on:** Phase 1
-**Requirements:** [REQ-IDs]
-
-**Success Criteria:**
-1. [Observable user behavior]
-2. [Observable user behavior]
-
----
+Use template from `~/.claude/get-shit-done/templates/roadmap.md`.
 
-[... more phases ...]
-
-## Progress
-
-| Phase | Status | Completed |
-|-------|--------|-----------|
-| 1 - [Name] | Not started | — |
-| 2 - [Name] | Not started | — |
-| 3 - [Name] | Not started | — |
-
----
-
-*Roadmap for milestone: v1.0*
-```
+Key sections:
+- Overview (2-3 sentences)
+- Phases with Goal, Dependencies, Requirements, Success Criteria
+- Progress table
 
 ## STATE.md Structure
 
-```markdown
-# Project State
-
-## Project Reference
-
-See: .planning/PROJECT.md
-
-**Core value:** [from PROJECT.md]
-**Current focus:** Phase 1 — [name]
-
-## Current Position
-
-Phase: 1 of [N] ([name])
-Plan: Not started
-Status: Ready to plan
-Last activity: [date] — Project initialized
-
-Progress: ░░░░░░░░░░ 0%
-
-## Performance Metrics
-
-**Velocity:**
-- Total plans completed: 0
-- Average duration: —
-
-**By Phase:**
+Use template from `~/.claude/get-shit-done/templates/state.md`.
 
-| Phase | Plans | Total | Avg/Plan |
-|-------|-------|-------|----------|
-| — | — | — | — |
-
-## Accumulated Context
-
-### Decisions
-
-(None yet)
-
-### Pending Todos
-
-(None yet)
-
-### Blockers/Concerns
-
-(None yet)
-
-## Session Continuity
-
-Last session: [date]
-Stopped at: Project initialization
-Resume file: None
-```
+Key sections:
+- Project Reference (core value, current focus)
+- Current Position (phase, plan, status, progress bar)
+- Performance Metrics
+- Accumulated Context (decisions, todos, blockers)
+- Session Continuity
 
 ## Draft Presentation Format
 

package/commands/gsd/audit-milestone.md

@@ -143,9 +143,12 @@ Route by status (see `<offer_next>`).
 </process>
 
 <offer_next>
+Output this markdown directly (not as a code block). Route based on status:
+
+---
+
 **If passed:**
 
-```markdown
 ## ✓ Milestone {version} — Audit Passed
 
 **Score:** {N}/{M} requirements satisfied
@@ -153,22 +156,22 @@ Route by status (see `<offer_next>`).
 
 All requirements covered. Cross-phase integration verified. E2E flows complete.
 
----
+───────────────────────────────────────────────────────────────
 
 ## ▶ Next Up
 
 **Complete milestone** — archive and tag
 
-`/gsd:complete-milestone {version}`
+/gsd:complete-milestone {version}
 
-<sub>`/clear` first → fresh context window</sub>
-```
+<sub>/clear first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
 
 ---
 
 **If gaps_found:**
 
-```markdown
 ## ⚠ Milestone {version} — Gaps Found
 
 **Score:** {N}/{M} requirements satisfied
@@ -190,28 +193,28 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 {For each flow gap:}
 - **{flow name}:** breaks at {step}
 
----
+───────────────────────────────────────────────────────────────
 
 ## ▶ Next Up
 
 **Plan gap closure** — create phases to complete milestone
 
-`/gsd:plan-milestone-gaps`
+/gsd:plan-milestone-gaps
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>/clear first → fresh context window</sub>
 
----
+───────────────────────────────────────────────────────────────
 
 **Also available:**
-- `cat .planning/v{version}-MILESTONE-AUDIT.md` — see full report
-- `/gsd:complete-milestone {version}` — proceed anyway (accept tech debt)
-```
+- cat .planning/v{version}-MILESTONE-AUDIT.md — see full report
+- /gsd:complete-milestone {version} — proceed anyway (accept tech debt)
+
+───────────────────────────────────────────────────────────────
 
 ---
 
 **If tech_debt (no blockers but accumulated debt):**
 
-```markdown
 ## ⚡ Milestone {version} — Tech Debt Review
 
 **Score:** {N}/{M} requirements satisfied
@@ -228,20 +231,21 @@ All requirements met. No critical blockers. Accumulated tech debt needs review.
 
 ### Total: {N} items across {M} phases
 
----
+───────────────────────────────────────────────────────────────
 
 ## ▶ Options
 
 **A. Complete milestone** — accept debt, track in backlog
 
-`/gsd:complete-milestone {version}`
+/gsd:complete-milestone {version}
 
 **B. Plan cleanup phase** — address debt before completing
 
-`/gsd:plan-milestone-gaps`
+/gsd:plan-milestone-gaps
 
-<sub>`/clear` first → fresh context window</sub>
-```
+<sub>/clear first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
 </offer_next>
 
 <success_criteria>

package/commands/gsd/complete-milestone.md

@@ -108,8 +108,7 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
    - Ask about pushing tag
 
 8. **Offer next steps:**
-   - `/gsd:discuss-milestone` — thinking partner, creates context file
-   - Then `/gsd:new-milestone` — update PROJECT.md with new goals
+   - `/gsd:new-milestone` — start next milestone (questioning → research → requirements → roadmap)
 
 </process>
 
@@ -133,5 +132,5 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 - **Archive before deleting:** Always create archive files before updating/deleting originals
 - **One-line summary:** Collapsed milestone in ROADMAP.md should be single line with link
 - **Context efficiency:** Archive keeps ROADMAP.md and REQUIREMENTS.md constant size per milestone
-- **Fresh requirements:** Next milestone starts with `/gsd:define-requirements`, not reusing old file
+- **Fresh requirements:** Next milestone starts with `/gsd:new-milestone` which includes requirements definition
   </critical_rules>

package/commands/gsd/execute-phase.md

@@ -105,9 +105,7 @@ Phase: $ARGUMENTS
 </process>
 
 <offer_next>
-**MANDATORY: Present copy/paste-ready next command.**
-
-After verification completes, route based on status:
+Output this markdown directly (not as a code block). Route based on status:
 
 | Status | Route |
 |--------|-------|
@@ -120,7 +118,6 @@ After verification completes, route based on status:
 
 **Route A: Phase verified, more phases remain**
 
-```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  GSD ► PHASE {Z} COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -136,24 +133,22 @@ Goal verified ✓
 
 **Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
 
-`/gsd:plan-phase {Z+1}`
+/gsd:discuss-phase {Z+1} — gather context and clarify approach
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>/clear first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
-- `/gsd:verify-work {Z}` — manual acceptance testing before continuing
-- `/gsd:discuss-phase {Z+1}` — gather context first
+- /gsd:plan-phase {Z+1} — skip discussion, plan directly
+- /gsd:verify-work {Z} — manual acceptance testing before continuing
 
 ───────────────────────────────────────────────────────────────
-```
 
 ---
 
 **Route B: Phase verified, milestone complete**
 
-```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  GSD ► MILESTONE COMPLETE 🎉
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -169,24 +164,22 @@ All phase goals verified ✓
 
 **Audit milestone** — verify requirements, cross-phase integration, E2E flows
 
-`/gsd:audit-milestone`
+/gsd:audit-milestone
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>/clear first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
-- `/gsd:verify-work` — manual acceptance testing
-- `/gsd:complete-milestone` — skip audit, archive directly
+- /gsd:verify-work — manual acceptance testing
+- /gsd:complete-milestone — skip audit, archive directly
 
 ───────────────────────────────────────────────────────────────
-```
 
 ---
 
 **Route C: Gaps found — need additional planning**
 
-```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  GSD ► PHASE {Z} GAPS FOUND ⚠
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -194,7 +187,7 @@ All phase goals verified ✓
 **Phase {Z}: {Name}**
 
 Score: {N}/{M} must-haves verified
-Report: `.planning/phases/{phase_dir}/{phase}-VERIFICATION.md`
+Report: .planning/phases/{phase_dir}/{phase}-VERIFICATION.md
 
 ### What's Missing
 
@@ -206,23 +199,24 @@ Report: `.planning/phases/{phase_dir}/{phase}-VERIFICATION.md`
 
 **Plan gap closure** — create additional plans to complete the phase
 
-`/gsd:plan-phase {Z} --gaps`
+/gsd:plan-phase {Z} --gaps
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>/clear first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
-- `cat .planning/phases/{phase_dir}/{phase}-VERIFICATION.md` — see full report
-- `/gsd:verify-work {Z}` — manual testing before planning
+- cat .planning/phases/{phase_dir}/{phase}-VERIFICATION.md — see full report
+- /gsd:verify-work {Z} — manual testing before planning
 
 ───────────────────────────────────────────────────────────────
-```
 
-After user runs `/gsd:plan-phase {Z} --gaps`:
+---
+
+After user runs /gsd:plan-phase {Z} --gaps:
 1. Planner reads VERIFICATION.md gaps
 2. Creates plans 04, 05, etc. to close gaps
-3. User runs `/gsd:execute-phase {Z}` again
+3. User runs /gsd:execute-phase {Z} again
 4. Execute-phase runs incomplete plans (04, 05...)
 5. Verifier runs again → loop until passed
 </offer_next>

package/commands/gsd/help.md

@@ -76,14 +76,6 @@ Map an existing codebase for brownfield projects.
 
 Usage: `/gsd:map-codebase`
 
-### Standalone Commands (deprecated, kept for mid-project use)
-
-These commands are now integrated into `/gsd:new-project` but remain available for mid-project adjustments:
-
-**`/gsd:research-project`** — Re-research a domain (integrated into new-project Phase 6)
-**`/gsd:define-requirements`** — Redefine requirements (integrated into new-project Phase 7)
-**`/gsd:create-roadmap`** — Recreate roadmap (integrated into new-project Phase 8)
-
 ### Phase Planning
 
 **`/gsd:discuss-phase <number>`**
@@ -171,21 +163,15 @@ Result: Phase 17 deleted, phases 18-20 become 17-19
 
 ### Milestone Management
 
-**`/gsd:discuss-milestone`**
-Figure out what you want to build in the next milestone.
-
-- Reviews what shipped in previous milestone
-- Helps you identify features to add, improve, or fix
-- Routes to /gsd:new-milestone when ready
-
-Usage: `/gsd:discuss-milestone`
-
 **`/gsd:new-milestone <name>`**
-Create a new milestone with phases for an existing project.
+Start a new milestone through unified flow.
+
+- Deep questioning to understand what you're building next
+- Optional domain research (spawns 4 parallel researcher agents)
+- Requirements definition with scoping
+- Roadmap creation with phase breakdown
 
-- Adds milestone section to ROADMAP.md
-- Creates phase directories
-- Updates STATE.md for new milestone
+Mirrors `/gsd:new-project` flow for brownfield projects (existing PROJECT.md).
 
 Usage: `/gsd:new-milestone "v2.0 Features"`
 
@@ -366,7 +352,8 @@ Change anytime by editing `.planning/config.json`
 
 ```
 /gsd:complete-milestone 1.0.0
-/gsd:new-milestone  # Start next milestone
+/clear
+/gsd:new-milestone  # Start next milestone (questioning → research → requirements → roadmap)
 ```
 
 **Capturing ideas during work:**