get-shit-done-cc 1.3.25 → 1.3.26

package/README.md

@@ -14,17 +14,38 @@
 *"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.
+## Who This Is For
 
-_Warning: Not for people who enjoy inconsistent and sloppy results._
+People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.
+
+---
+
+## Why I Built This
+
+I'm a solo developer. I don't write code — Claude Code does.
+
+Other spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work.
+
+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.
+
+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.
+
+— TÂCHES
 
 ---
 
@@ -49,22 +70,6 @@ Verify: `/gsd:help`
 
 ---
 
-## Why I Built This
-
-I'm a solo developer. I don't write code — Claude Code does.
-
-Other spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work.
-
-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.
-
-That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.
-
-— TÂCHES
-
----
-
 ## How It Works
 
 ### 1. Start with an idea
@@ -249,20 +254,10 @@ You're never locked in. The system adapts.
 
 ---
 
-## Who This Is For
-
-People who want to vibecode and have it actually work.
-
-Anyone who wants to clearly describe what they want, trust the system to build it, and go live their life.
-
-Not for people who enjoy inconsistent and sloppy results.
-
----
-
 ## License
 
 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/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:**

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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-done-cc",
-  "version": "1.3.25",
+  "version": "1.3.26",
   "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"