get-shit-done-cc 1.3.25 → 1.3.27

package/README.md

@@ -14,38 +14,42 @@
 *"By far the most powerful addition to my Claude Code. Nothing over-engineered. Literally just gets shit done."*
 
 <br>
+
+**Trusted by engineers at Amazon, Google, Shopify, and Webflow.**
+
 </div>
 
 ---
 
 Vibecoding has a bad reputation. You describe what you want, AI generates code, and you get inconsistent garbage that falls apart at scale.
 
-GSD fixes that. It's the context engineering layer that makes Claude Code reliable. Describe your idea, let the system extract everything it needs to know, and then let Claude Code get to work.
+GSD fixes that. It's the context engineering layer that makes Claude Code reliable. Describe your idea, let the system extract everything it needs to know, and let Claude Code get to work.
 
-THIS is how you vibecode and actually get shit done.
+---
 
-_Warning: Not for people who enjoy inconsistent and sloppy results._
+## Who This Is For
 
----
+People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.
 
-## Installation
+### Marketplace Installation
+
+Install from the Claude Code marketplace:
 
 ```bash
-npx get-shit-done-cc
+/plugin marketplace add glittercowboy/get-shit-done
+/plugin install get-shit-done@get-shit-done
 ```
 
-That's it. Works on Mac, Windows, and Linux.
+### Manual Installation
 
-### Non-interactive Install (Docker, CI, Scripts)
+Clone the repository and tell Claude Code where to find it:
 
 ```bash
-npx get-shit-done-cc --global   # Install to ~/.claude/
-npx get-shit-done-cc --local    # Install to ./.claude/
+git clone https://github.com/glittercowboy/get-shit-done.git
+claude --plugin-dir ./get-shit-done
 ```
 
-Use `--global` (`-g`) or `--local` (`-l`) to skip the interactive prompt.
-
-Verify: `/gsd:help`
+Useful for development or testing modifications.
 
 ---
 
@@ -57,7 +61,7 @@ Other spec-driven development tools exist; BMAD, Speckit... But they all seem to
 
 So I built GSD. The complexity is in the system, not in your workflow. Behind the scenes: context engineering, XML prompt formatting, subagent orchestration, state management. What you see: a few commands that just work.
 
-I wanted to spend my time having ideas and seeing them through to implementation — not babysitting Claude. Now I can say "go," put it in YOLO mode, and go to the beach. The system gives Claude everything it needs to do the work _and_ verify it. I trust the workflow. It just does a good job.
+The system gives Claude everything it needs to do the work _and_ verify it. I trust the workflow. It just does a good job.
 
 That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.
 
@@ -65,6 +69,70 @@ That's what this is. No enterprise roleplay bullshit. Just an incredibly effecti
 
 ---
 
+## Installation
+
+```bash
+npx get-shit-done-cc
+```
+
+That's it. Works on Mac, Windows, and Linux.
+
+### Non-interactive Install (Docker, CI, Scripts)
+
+```bash
+npx get-shit-done-cc --global   # Install to ~/.claude/
+npx get-shit-done-cc --local    # Install to ./.claude/
+```
+
+Use `--global` (`-g`) or `--local` (`-l`) to skip the interactive prompt.
+
+Verify: `/gsd:help`
+
+### Recommended: Skip Permissions Mode
+
+GSD is designed for frictionless automation. Run Claude Code with:
+
+```bash
+claude --dangerously-skip-permissions
+```
+
+This is how GSD is intended to be used — stopping to approve `date` and `git commit` 50 times defeats the purpose.
+
+If you prefer not to use that flag, add this to your project's `.claude/settings.json` to auto-approve GSD's commands:
+
+<details>
+<summary>Show settings.json permissions</summary>
+
+```json
+{
+  "permissions": {
+    "allow": [
+      "Bash(date:*)",
+      "Bash(echo:*)",
+      "Bash(cat:*)",
+      "Bash(ls:*)",
+      "Bash(mkdir:*)",
+      "Bash(wc:*)",
+      "Bash(head:*)",
+      "Bash(tail:*)",
+      "Bash(sort:*)",
+      "Bash(grep:*)",
+      "Bash(tr:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(git status:*)",
+      "Bash(git log:*)",
+      "Bash(git diff:*)",
+      "Bash(git tag:*)"
+    ]
+  }
+}
+```
+
+</details>
+
+---
+
 ## How It Works
 
 ### 1. Start with an idea
@@ -249,13 +317,15 @@ You're never locked in. The system adapts.
 
 ---
 
-## Who This Is For
-
-People who want to vibecode and have it actually work.
+## Troubleshooting
 
-Anyone who wants to clearly describe what they want, trust the system to build it, and go live their life.
+**Plugin not found after install?**
+- Restart Claude Code to reload plugins
+- Check `/plugins` to see installed plugins
 
-Not for people who enjoy inconsistent and sloppy results.
+**Commands showing as unavailable?**
+- Verify plugin directory structure: should have `.claude-plugin/plugin.json`
+- Try `/gsd:help` - if it works, plugin is loaded correctly
 
 ---
 
@@ -265,4 +335,4 @@ MIT License. See [LICENSE](LICENSE) for details.
 
 ---
 
-**Claude Code is powerful. GSD gives it the context and the systematic consistency to prove it.**
+**Claude Code is powerful. GSD makes it reliable.**

package/commands/gsd/add-phase.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:add-phase
 description: Add phase to end of current milestone in roadmap
 argument-hint: <description>
 allowed-tools:

package/commands/gsd/complete-milestone.md

@@ -1,5 +1,6 @@
 ---
 type: prompt
+name: gsd:complete-milestone
 description: Archive completed milestone and prepare for next version
 argument-hint: <version>
 allowed-tools:

package/commands/gsd/consider-issues.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:consider-issues
 description: Review deferred issues with codebase context, close resolved ones, identify urgent ones
 allowed-tools:
   - Read

package/commands/gsd/create-roadmap.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:create-roadmap
 description: Create roadmap with phases for the project
 allowed-tools:
   - Read

package/commands/gsd/discuss-milestone.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:discuss-milestone
 description: Gather context for next milestone through adaptive questioning
 ---
 

package/commands/gsd/discuss-phase.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:discuss-phase
 description: Gather phase context through adaptive questioning before planning
 argument-hint: "[phase]"
 ---

package/commands/gsd/execute-plan.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:execute-plan
 description: Execute a PLAN.md file
 argument-hint: "[path-to-PLAN.md]"
 allowed-tools:

package/commands/gsd/help.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:help
 description: Show available GSD commands and usage guide
 ---
 

package/commands/gsd/insert-phase.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:insert-phase
 description: Insert urgent work as decimal phase (e.g., 72.1) between existing phases
 argument-hint: <after> <description>
 allowed-tools:

package/commands/gsd/list-phase-assumptions.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:list-phase-assumptions
 description: Surface Claude's assumptions about a phase approach before planning
 argument-hint: "[phase]"
 allowed-tools:

package/commands/gsd/map-codebase.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:map-codebase
 description: Analyze codebase with parallel Explore agents to produce .planning/codebase/ documents
 argument-hint: "[optional: specific area to map, e.g., 'api' or 'auth']"
 allowed-tools:

package/commands/gsd/new-milestone.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:new-milestone
 description: Create a new milestone with phases for an existing project
 argument-hint: "[milestone name, e.g., 'v2.0 Features']"
 ---

package/commands/gsd/new-project.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:new-project
 description: Initialize a new project with deep context gathering and PROJECT.md
 allowed-tools:
   - Read

package/commands/gsd/pause-work.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:pause-work
 description: Create context handoff when pausing work mid-phase
 allowed-tools:
   - Read

package/commands/gsd/plan-phase.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:plan-phase
 description: Create detailed execution plan for a phase (PLAN.md)
 argument-hint: "[phase]"
 allowed-tools:

package/commands/gsd/progress.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:progress
 description: Check project progress, show context, and route to next action (execute or plan)
 allowed-tools:
   - Read
@@ -89,84 +90,164 @@ CONTEXT: [✓ if CONTEXT.md exists | - if not]
 </step>
 
 <step name="route">
-**Determine next action:**
+**Determine next action based on verified counts.**
 
-Find the next plan number that needs work.
-Check if `{phase}-{plan}-PLAN.md` exists for that number.
+**Step 1: Count plans and summaries in current phase**
 
-**If PLAN.md exists (unexecuted):**
+List files in the current phase directory:
 
-- Read its `<objective>` section
-- Show: "Ready to execute: [path] - [objective summary]"
-- Display (see ~/.claude/get-shit-done/references/continuation-format.md):
-  ```
-  ---
+```bash
+ls -1 .planning/phases/[current-phase-dir]/*-PLAN.md 2>/dev/null | wc -l
+ls -1 .planning/phases/[current-phase-dir]/*-SUMMARY.md 2>/dev/null | wc -l
+```
+
+State: "This phase has {X} plans and {Y} summaries."
 
-  ## ▶ Next Up
+**Step 2: Route based on counts**
 
-  **{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
+| Condition | Meaning | Action |
+|-----------|---------|--------|
+| summaries < plans | Unexecuted plans exist | Go to **Route A** |
+| summaries = plans AND plans > 0 | Phase complete | Go to Step 3 |
+| plans = 0 | Phase not yet planned | Go to **Route B** |
 
-  `/gsd:execute-plan [full-path-to-PLAN.md]`
+---
 
-  <sub>`/clear` first → fresh context window</sub>
+**Route A: Unexecuted plan exists**
 
-  ---
-  ```
+Find the first PLAN.md without matching SUMMARY.md.
+Read its `<objective>` section.
 
-**If PLAN.md does NOT exist:**
+```
+---
 
-- Check if `{phase}-CONTEXT.md` exists in phase directory
-- Show: "Next plan not yet created: [expected path]"
-- Show phase objective from ROADMAP
+## ▶ Next Up
+
+**{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
+
+`/gsd:execute-plan [full-path-to-PLAN.md]`
+
+<sub>`/clear` first → fresh context window</sub>
+
+---
+```
+
+---
+
+**Route B: Phase needs planning**
+
+Check if `{phase}-CONTEXT.md` exists in phase directory.
 
 **If CONTEXT.md exists:**
 
-- Display: "✓ Context gathered, ready to plan"
-- Display:
-  ```
-  ---
+```
+---
 
-  ## ▶ Next Up
+## ▶ Next Up
 
-  **Phase [N]: [Name]** — [Goal from ROADMAP.md]
+**Phase {N}: {Name}** — {Goal from ROADMAP.md}
+<sub>✓ Context gathered, ready to plan</sub>
 
-  `/gsd:plan-phase [phase-number]`
+`/gsd:plan-phase {phase-number}`
 
-  <sub>`/clear` first → fresh context window</sub>
+<sub>`/clear` first → fresh context window</sub>
 
-  ---
-  ```
+---
+```
 
 **If CONTEXT.md does NOT exist:**
 
-- Display:
-  ```
-  ---
+```
+---
+
+## ▶ Next Up
+
+**Phase {N}: {Name}** — {Goal from ROADMAP.md}
+
+`/gsd:plan-phase {phase}`
+
+<sub>`/clear` first → fresh context window</sub>
 
-  ## ▶ Next Up
+---
+
+**Also available:**
+- `/gsd:discuss-phase {phase}` — gather context first
+- `/gsd:research-phase {phase}` — investigate unknowns
+- `/gsd:list-phase-assumptions {phase}` — see Claude's assumptions
+
+---
+```
 
-  **Phase [N]: [Name]** — [Goal from ROADMAP.md]
+---
 
-  `/gsd:plan-phase [phase]`
+**Step 3: Check milestone status (only when phase complete)**
 
-  <sub>`/clear` first → fresh context window</sub>
+Read ROADMAP.md and identify:
+1. Current phase number
+2. All phase numbers in the current milestone section
 
-  ---
+Count total phases and identify the highest phase number.
 
-  **Also available:**
-  - `/gsd:discuss-phase [phase]` — gather context first
-  - `/gsd:research-phase [phase]` — investigate unknowns
-  - `/gsd:list-phase-assumptions [phase]` — see Claude's assumptions
+State: "Current phase is {X}. Milestone has {N} phases (highest: {Y})."
 
-  ---
-  ```
+**Route based on milestone status:**
 
-**If all plans complete for current phase:**
+| Condition | Meaning | Action |
+|-----------|---------|--------|
+| current phase < highest phase | More phases remain | Go to **Route C** |
+| current phase = highest phase | Milestone complete | Go to **Route D** |
 
-- Check if more phases exist in ROADMAP
-- If yes: Show `/gsd:plan-phase [next-phase]` command to paste
-- If no (milestone 100% complete): Show `/gsd:complete-milestone` command to paste
-  </step>
+---
+
+**Route C: Phase complete, more phases remain**
+
+Read ROADMAP.md to get the next phase's name and goal.
+
+```
+---
+
+## ✓ Phase {Z} Complete
+
+## ▶ Next Up
+
+**Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
+
+`/gsd:plan-phase {Z+1}`
+
+<sub>`/clear` first → fresh context window</sub>
+
+---
+
+**Also available:**
+- `/gsd:discuss-phase {Z+1}` — gather context first
+- `/gsd:research-phase {Z+1}` — investigate unknowns
+
+---
+```
+
+---
+
+**Route D: Milestone complete**
+
+```
+---
+
+## 🎉 Milestone Complete
+
+All {N} phases finished!
+
+## ▶ Next Up
+
+**Complete Milestone** — archive and prepare for next
+
+`/gsd:complete-milestone`
+
+<sub>`/clear` first → fresh context window</sub>
+
+---
+```
+
+</step>
 
 <step name="edge_cases">
 **Handle edge cases:**

package/commands/gsd/research-phase.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:research-phase
 description: Research how to implement a phase before planning
 argument-hint: "[phase]"
 allowed-tools:

package/commands/gsd/resume-work.md

@@ -1,4 +1,5 @@
 ---
+name: gsd:resume-work
 description: Resume work from previous session with full context restoration
 allowed-tools:
   - Read

package/get-shit-done/workflows/discuss-phase.md

@@ -215,6 +215,25 @@ Created: .planning/phases/${PHASE}-${SLUG}/${PHASE}-CONTEXT.md
 
 </step>
 
+<step name="git_commit">
+Commit phase context:
+
+```bash
+git add .planning/phases/${PHASE}-${SLUG}/${PHASE}-CONTEXT.md
+git commit -m "$(cat <<'EOF'
+docs(${PHASE}): capture phase context
+
+Phase ${PHASE}: ${PHASE_NAME}
+- Vision and goals documented
+- Essential requirements identified
+- Scope boundaries defined
+EOF
+)"
+```
+
+Confirm: "Committed: docs(${PHASE}): capture phase context"
+</step>
+
 </process>
 
 <success_criteria>
@@ -223,5 +242,6 @@ Created: .planning/phases/${PHASE}-${SLUG}/${PHASE}-CONTEXT.md
 - Vision gathered through collaborative thinking (not interrogation)
 - User's imagination captured: how it works, what's essential, what's out of scope
 - CONTEXT.md created in phase directory
+- CONTEXT.md committed to git
 - User knows next steps (typically: research or plan the phase)
 </success_criteria>

package/get-shit-done/workflows/execute-phase.md

@@ -1285,15 +1285,14 @@ ROADMAP_FILE=".planning/ROADMAP.md"
   </step>
 
 <step name="git_commit_metadata">
-Commit plan metadata (SUMMARY + STATE + ROADMAP):
+Commit execution metadata (SUMMARY + STATE + ROADMAP):
 
 **Note:** All task code has already been committed during execution (one commit per task).
-This final commit captures plan completion metadata only.
+PLAN.md was already committed during plan-phase. This final commit captures execution results only.
 
-**1. Stage planning artifacts:**
+**1. Stage execution artifacts:**
 
 ```bash
-git add .planning/phases/XX-name/{phase}-{plan}-PLAN.md
 git add .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
 git add .planning/STATE.md
 ```
@@ -1308,7 +1307,7 @@ git add .planning/ROADMAP.md
 
 ```bash
 git status
-# Should show only planning artifacts, no code files
+# Should show only execution artifacts (SUMMARY, STATE, ROADMAP), no code files
 ```
 
 **4. Commit metadata:**
@@ -1438,33 +1437,44 @@ Use AskUserQuestion:
 </step>
 
 <step name="offer_next">
-**First, determine if more plans exist in this phase:**
+**MANDATORY: Verify remaining work before presenting next steps.**
 
-```bash
-# Get current phase directory from the plan we just executed
-PHASE_DIR=$(dirname "$PLAN_PATH")
+Do NOT skip this verification. Do NOT assume phase or milestone completion without checking.
 
-# Count PLAN files vs SUMMARY files
-PLAN_COUNT=$(ls "$PHASE_DIR"/*-PLAN.md 2>/dev/null | wc -l | tr -d ' ')
-SUMMARY_COUNT=$(ls "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null | wc -l | tr -d ' ')
+**Step 1: Count plans and summaries in current phase**
 
-echo "Plans: $PLAN_COUNT, Summaries: $SUMMARY_COUNT"
+List files in the phase directory:
 
-if [[ $SUMMARY_COUNT -lt $PLAN_COUNT ]]; then
-  echo "MORE_PLANS_EXIST"
-else
-  echo "PHASE_COMPLETE"
-fi
+```bash
+ls -1 .planning/phases/[current-phase-dir]/*-PLAN.md 2>/dev/null | wc -l
+ls -1 .planning/phases/[current-phase-dir]/*-SUMMARY.md 2>/dev/null | wc -l
 ```
 
-**If MORE_PLANS_EXIST (more plans in this phase):**
+State the counts: "This phase has [X] plans and [Y] summaries."
+
+**Step 2: Route based on plan completion**
+
+Compare the counts from Step 1:
+
+| Condition | Meaning | Action |
+|-----------|---------|--------|
+| summaries < plans | More plans remain | Go to **Route A** |
+| summaries = plans | Phase complete | Go to Step 3 |
+
+---
+
+**Route A: More plans remain in this phase**
+
+Identify the next unexecuted plan:
+- Find the first PLAN.md file that has no matching SUMMARY.md
+- Read its `<objective>` section
 
 <if mode="yolo">
 ```
 Plan {phase}-{plan} complete.
-Summary: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
+Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 
-[X] of [Y] plans complete for Phase Z.
+{Y} of {X} plans complete for Phase {Z}.
 
 ⚡ Auto-continuing: Execute next plan ({phase}-{next-plan})
 ```
@@ -1475,9 +1485,9 @@ Loop back to identify_plan step automatically.
 <if mode="interactive" OR="custom with gates.execute_next_plan true">
 ```
 Plan {phase}-{plan} complete.
-Summary: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
+Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 
-[X] of [Y] plans complete for Phase Z.
+{Y} of {X} plans complete for Phase {Z}.
 
 ---
 
@@ -1485,7 +1495,7 @@ Summary: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
 
 **{phase}-{next-plan}: [Plan Name]** — [objective from next PLAN.md]
 
-`/gsd:execute-plan .planning/phases/XX-name/{phase}-{next-plan}-PLAN.md`
+`/gsd:execute-plan .planning/phases/{phase-dir}/{phase}-{next-plan}-PLAN.md`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -1500,84 +1510,99 @@ Summary: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
 Wait for user to clear and run next command.
 </if>
 
-**If phase complete (last plan done):**
+**STOP here if Route A applies. Do not continue to Step 3.**
 
-First, check if this is also the last phase in the milestone (milestone complete):
+---
 
-```bash
-# Count total phases in ROADMAP.md
-TOTAL_PHASES=$(grep -c "^### Phase [0-9]" .planning/ROADMAP.md)
+**Step 3: Check milestone status (only when all plans in phase are complete)**
 
-# Get current phase number from the just-completed plan
-CURRENT_PHASE=$(echo "{phase}" | grep -oE '^[0-9]+')
+Read ROADMAP.md and extract:
+1. Current phase number (from the plan just completed)
+2. All phase numbers listed in the current milestone section
 
-# Check if current phase == total phases
-if [[ "$CURRENT_PHASE" -eq "$TOTAL_PHASES" ]]; then
-  # Milestone complete
-  MILESTONE_COMPLETE=true
-fi
-```
+To find phases in the current milestone, look for:
+- Phase headers: lines starting with `### Phase` or `#### Phase`
+- Phase list items: lines like `- [ ] **Phase X:` or `- [x] **Phase X:`
 
-**If milestone complete (final phase of roadmap done):**
+Count total phases in the current milestone and identify the highest phase number.
 
-```
-🎉 MILESTONE COMPLETE!
+State: "Current phase is {X}. Milestone has {N} phases (highest: {Y})."
+
+**Step 4: Route based on milestone status**
+
+| Condition | Meaning | Action |
+|-----------|---------|--------|
+| current phase < highest phase | More phases remain | Go to **Route B** |
+| current phase = highest phase | Milestone complete | Go to **Route C** |
+
+---
 
+**Route B: Phase complete, more phases remain in milestone**
+
+Read ROADMAP.md to get the next phase's name and goal.
+
+```
 Plan {phase}-{plan} complete.
-Summary: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
+Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 
-Phase [Z]: [Name] COMPLETE - all [Y] plans finished.
+## ✓ Phase {Z}: {Phase Name} Complete
 
-════════════════════════════════════════
-All [N] phases complete!
-This milestone is 100% done.
-════════════════════════════════════════
+All {Y} plans finished.
 
 ---
 
 ## ▶ Next Up
 
-**Complete Milestone** — archive and prepare for next
+**Phase {Z+1}: {Next Phase Name}** — {Goal from ROADMAP.md}
 
-`/gsd:complete-milestone`
+`/gsd:plan-phase {Z+1}`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/gsd:add-phase <description>` — add another phase
-- Review accomplishments before archiving
+- `/gsd:discuss-phase {Z+1}` — gather context first
+- `/gsd:research-phase {Z+1}` — investigate unknowns
+- Review phase accomplishments before continuing
 
 ---
 ```
 
-**If phase complete but more phases remain:**
+---
+
+**Route C: Milestone complete (all phases done)**
 
 ```
+🎉 MILESTONE COMPLETE!
+
 Plan {phase}-{plan} complete.
-Summary: .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
+Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 
-## ✓ Phase [Z] Complete
+## ✓ Phase {Z}: {Phase Name} Complete
 
-All [Y] plans finished.
+All {Y} plans finished.
+
+════════════════════════════════════════
+All {N} phases complete!
+Milestone is 100% done.
+════════════════════════════════════════
 
 ---
 
 ## ▶ Next Up
 
-**Phase [X+1]: [Name]** — [Goal from ROADMAP.md]
+**Complete Milestone** — archive and prepare for next
 
-`/gsd:plan-phase [X+1]`
+`/gsd:complete-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/gsd:discuss-phase [X+1]` — gather context first
-- `/gsd:research-phase [X+1]` — investigate unknowns
-- Review phase accomplishments before continuing
+- `/gsd:add-phase <description>` — add another phase before completing
+- Review accomplishments before archiving
 
 ---
 ```

package/get-shit-done/workflows/plan-phase.md

@@ -391,6 +391,30 @@ This ensures every PLAN.md gets optimal context automatically assembled via depe
 For multi-plan phases: each plan has focused scope, references previous plan summaries (via frontmatter selection), last plan's success criteria includes "Phase X complete".
 </step>
 
+<step name="git_commit">
+Commit phase plan(s):
+
+```bash
+# Stage all PLAN.md files for this phase
+git add .planning/phases/${PHASE}-*/${PHASE}-*-PLAN.md
+
+# Also stage DISCOVERY.md if it was created during mandatory_discovery
+git add .planning/phases/${PHASE}-*/DISCOVERY.md 2>/dev/null
+
+git commit -m "$(cat <<'EOF'
+docs(${PHASE}): create phase plan
+
+Phase ${PHASE}: ${PHASE_NAME}
+- [N] plan(s) created
+- [X] total tasks defined
+- Ready for execution
+EOF
+)"
+```
+
+Confirm: "Committed: docs(${PHASE}): create phase plan"
+</step>
+
 <step name="offer_next">
 ```
 Phase plan created: .planning/phases/XX-name/{phase}-01-PLAN.md
@@ -451,5 +475,6 @@ Phase planning complete when:
 - [ ] Each task: Type, Files (if auto), Action, Verify, Done
 - [ ] Checkpoints properly structured
 - [ ] If RESEARCH.md exists: "don't hand-roll" items NOT being custom-built
+- [ ] PLAN file(s) committed to git
 - [ ] User knows next steps
 </success_criteria>

package/get-shit-done/workflows/research-phase.md

@@ -378,6 +378,25 @@ What's next?
 ```
 </step>
 
+<step name="git_commit">
+Commit phase research:
+
+```bash
+git add .planning/phases/${PHASE}-${SLUG}/${PHASE}-RESEARCH.md
+git commit -m "$(cat <<'EOF'
+docs(${PHASE}): complete phase research
+
+Phase ${PHASE}: ${PHASE_NAME}
+- Standard stack identified
+- Architecture patterns documented
+- Common pitfalls catalogued
+EOF
+)"
+```
+
+Confirm: "Committed: docs(${PHASE}): complete phase research"
+</step>
+
 </process>
 
 <success_criteria>
@@ -394,6 +413,7 @@ What's next?
 - [ ] "Don't hand-roll" list is clear and actionable
 - [ ] Common pitfalls catalogued
 - [ ] Confidence levels assigned honestly
+- [ ] RESEARCH.md committed to git
 - [ ] User knows next steps (plan phase)
 </success_criteria>
 

package/get-shit-done/workflows/transition.md

@@ -408,14 +408,34 @@ Resume file: None
 
 <step name="offer_next_phase">
 
-**Check if there's a next phase in the current milestone:**
+**MANDATORY: Verify milestone status before presenting next steps.**
 
-Re-read the ROADMAP file:
+**Step 1: Read ROADMAP.md and identify phases in current milestone**
 
-- Parse current milestone version (e.g., "v1.0" from "## Current Milestone: v1.0 Foundation")
-- Look for phases after the current one in the current milestone section
-- If next phase exists: offer to plan it
-- If no next phase (milestone 100% complete): offer to complete milestone with parsed version
+Read the ROADMAP.md file and extract:
+1. Current phase number (the phase just transitioned from)
+2. All phase numbers in the current milestone section
+
+To find phases, look for:
+- Phase headers: lines starting with `### Phase` or `#### Phase`
+- Phase list items: lines like `- [ ] **Phase X:` or `- [x] **Phase X:`
+
+Count total phases and identify the highest phase number in the milestone.
+
+State: "Current phase is {X}. Milestone has {N} phases (highest: {Y})."
+
+**Step 2: Route based on milestone status**
+
+| Condition | Meaning | Action |
+|-----------|---------|--------|
+| current phase < highest phase | More phases remain | Go to **Route A** |
+| current phase = highest phase | Milestone complete | Go to **Route B** |
+
+---
+
+**Route A: More phases remain in milestone**
+
+Read ROADMAP.md to get the next phase's name and goal.
 
 **If next phase exists:**
 
@@ -460,36 +480,38 @@ Exit skill and invoke SlashCommand("/gsd:plan-phase [X+1]")
 
 </if>
 
-**If no next phase (milestone 100% complete):**
+---
+
+**Route B: Milestone complete (all phases done)**
 
 <if mode="yolo">
 
 ```
-Phase [X] marked complete.
+Phase {X} marked complete.
 
-🎉 Milestone [version] is 100% complete — all phases finished!
+🎉 Milestone {version} is 100% complete — all {N} phases finished!
 
 ⚡ Auto-continuing: Complete milestone and archive
 ```
 
-Exit skill and invoke SlashCommand("/gsd:complete-milestone [version]")
+Exit skill and invoke SlashCommand("/gsd:complete-milestone {version}")
 
 </if>
 
 <if mode="interactive" OR="custom with gates.confirm_transition true">
 
 ```
-## ✓ Phase [X] Complete
+## ✓ Phase {X}: {Phase Name} Complete
 
-🎉 Milestone [version] is 100% complete — all phases finished!
+🎉 Milestone {version} is 100% complete — all {N} phases finished!
 
 ---
 
 ## ▶ Next Up
 
-**Complete Milestone [version]** — archive and prepare for next
+**Complete Milestone {version}** — archive and prepare for next
 
-`/gsd:complete-milestone [version]`
+`/gsd:complete-milestone {version}`
 
 <sub>`/clear` first → fresh context window</sub>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-done-cc",
-  "version": "1.3.25",
+  "version": "1.3.27",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "get-shit-done-cc": "bin/install.js"