get-shit-done-cc 1.5.1 → 1.5.2

package/README.md

@@ -77,6 +77,20 @@ npx get-shit-done-cc
 
 That's it. Verify with `/gsd:help` inside your Claude Code interface.
 
+### Staying Updated
+
+GSD evolves fast. Check for updates periodically:
+
+```
+/gsd:whats-new
+```
+
+Update with:
+
+```bash
+npx get-shit-done-cc@latest
+```
+
 <details>
 <summary><strong>Non-interactive Install (Docker, CI, Scripts)</strong></summary>
 

package/commands/gsd/execute-phase.md

@@ -64,7 +64,16 @@ Phase: $ARGUMENTS
    - Report phase completion status
    - Update ROADMAP.md
 
-6. **Offer next steps**
+6. **Update requirements**
+   Phase is complete, so mark its requirements as Complete:
+   - Read ROADMAP.md, find this phase's `Requirements:` line (e.g., "AUTH-01, AUTH-02")
+   - Read REQUIREMENTS.md traceability table
+   - For each REQ-ID in this phase: change Status from "Pending" to "Complete"
+   - Write updated REQUIREMENTS.md
+   - Stage for commit: `git add .planning/REQUIREMENTS.md`
+   - Skip if: REQUIREMENTS.md doesn't exist, or phase has no Requirements line
+
+7. **Offer next steps**
    - Route to next action (see `<offer_next>`)
 </process>
 
@@ -207,5 +216,6 @@ After all tasks complete:
 - [ ] Each plan has SUMMARY.md
 - [ ] STATE.md reflects phase completion
 - [ ] ROADMAP.md updated
+- [ ] REQUIREMENTS.md updated (phase requirements marked Complete)
 - [ ] User informed of next steps
 </success_criteria>

package/commands/gsd/execute-plan.md

@@ -108,7 +108,20 @@ ls -1 .planning/phases/[phase-dir]/*-SUMMARY.md 2>/dev/null | wc -l
 | Condition | Action |
 |-----------|--------|
 | summaries < plans | More plans remain → Route A |
-| summaries = plans | Phase complete → Check milestone (Step 3) |
+| summaries = plans | Phase complete → Update requirements, then Step 3 |
+
+**Step 2.5: Update requirements (only when phase complete)**
+
+When summaries = plans, update REQUIREMENTS.md before presenting completion:
+
+1. Get phase number from completed plan path
+2. Read ROADMAP.md, find the phase's `Requirements:` line (e.g., "AUTH-01, AUTH-02")
+3. Read REQUIREMENTS.md traceability table
+4. For each REQ-ID in this phase: change Status from "Pending" to "Complete"
+5. Write updated REQUIREMENTS.md
+6. Stage for commit: `git add .planning/REQUIREMENTS.md`
+
+**Skip if:** REQUIREMENTS.md doesn't exist, or phase has no Requirements line in ROADMAP.md.
 
 ---
 
@@ -322,5 +335,6 @@ Templates for checkpoint handling:
 <success_criteria>
 - [ ] Plan executed (SUMMARY.md created)
 - [ ] All checkpoints handled
+- [ ] If phase complete: REQUIREMENTS.md updated (phase requirements marked Complete)
 - [ ] User informed of completion and next steps
 </success_criteria>

package/commands/gsd/help.md

@@ -26,6 +26,20 @@ Output ONLY the reference content below. Do NOT add:
 3. `/gsd:plan-phase <number>` - Create detailed plan for first phase
 4. `/gsd:execute-plan <path>` - Execute the plan
 
+## Staying Updated
+
+GSD evolves fast. Check for updates periodically:
+
+```
+/gsd:whats-new
+```
+
+Shows what changed since your installed version. Update with:
+
+```bash
+npx get-shit-done-cc@latest
+```
+
 ## Core Workflow
 
 ```

package/commands/gsd/new-project.md

@@ -215,50 +215,49 @@ Do not compress. Capture everything gathered.
 
 </step>
 
-<step name="mode">
+<step name="workflow_preferences">
 
-Ask workflow mode preference:
+Ask all workflow preferences in a single AskUserQuestion call (3 questions):
 
-Use AskUserQuestion:
-
-- header: "Mode"
-- question: "How do you want to work?"
-- options:
-  - "YOLO" — Auto-approve, just execute (Recommended)
-  - "Interactive" — Confirm at each step
-
-</step>
-
-<step name="depth">
-
-Ask planning depth preference:
-
-Use AskUserQuestion:
-
-- header: "Depth"
-- question: "How thorough should planning be?"
-- options:
-  - "Quick" — Ship fast, minimal phases/plans (3-5 phases, 1-3 plans each)
-  - "Standard" — Balanced scope and speed (5-8 phases, 3-5 plans each)
-  - "Comprehensive" — Thorough coverage, more phases/plans (8-12 phases, 5-10 plans each)
+Use AskUserQuestion with questions array:
 
-**Depth controls compression tolerance, not artificial inflation.** All depths use 2-3 tasks per plan. Comprehensive means "don't compress complex work"—it doesn't mean "pad simple work to hit a number."
-
-</step>
-
-<step name="parallelization">
-
-Ask parallel execution preference:
-
-Use AskUserQuestion:
-
-- header: "Parallelization"
-- question: "Enable parallel phase execution?"
-- options:
-  - "Enabled" — Run independent plans in parallel (Recommended)
-  - "Disabled" — Execute plans sequentially
+```
+questions: [
+  {
+    header: "Mode",
+    question: "How do you want to work?",
+    multiSelect: false,
+    options: [
+      { label: "YOLO (Recommended)", description: "Auto-approve, just execute" },
+      { label: "Interactive", description: "Confirm at each step" }
+    ]
+  },
+  {
+    header: "Depth",
+    question: "How thorough should planning be?",
+    multiSelect: false,
+    options: [
+      { label: "Quick", description: "Ship fast (3-5 phases, 1-3 plans each)" },
+      { label: "Standard", description: "Balanced scope and speed (5-8 phases, 3-5 plans each)" },
+      { label: "Comprehensive", description: "Thorough coverage (8-12 phases, 5-10 plans each)" }
+    ]
+  },
+  {
+    header: "Execution",
+    question: "Run plans in parallel?",
+    multiSelect: false,
+    options: [
+      { label: "Parallel (Recommended)", description: "Independent plans run simultaneously" },
+      { label: "Sequential", description: "One plan at a time" }
+    ]
+  }
+]
+```
 
-**Parallelization** spawns multiple agents for independent plans within a phase. Wave-based execution handles dependencies automatically. Can be changed later in config.json.
+**Notes:**
+- Depth controls compression tolerance, not artificial inflation
+- Parallelization spawns multiple agents for independent plans
+- All settings can be changed later in config.json
 
 </step>
 

package/commands/gsd/plan-phase.md

@@ -39,6 +39,20 @@ Phase number: $ARGUMENTS (optional - auto-detects next unplanned phase if not pr
 **Load roadmap:**
 @.planning/ROADMAP.md
 
+**Load requirements:**
+@.planning/REQUIREMENTS.md
+
+After loading, extract the requirements for the current phase:
+1. Find the phase in ROADMAP.md, get its `Requirements:` list (e.g., "PROF-01, PROF-02, PROF-03")
+2. Look up each REQ-ID in REQUIREMENTS.md to get the full description
+3. Present the requirements this phase must satisfy:
+   ```
+   Phase [N] Requirements:
+   - PROF-01: User can create profile with display name
+   - PROF-02: User can upload avatar image
+   - PROF-03: User can write bio (max 500 chars)
+   ```
+
 **Load phase context if exists (created by /gsd:discuss-phase):**
 Check for and read `.planning/phases/XX-name/{phase}-CONTEXT.md` - contains research findings, clarifications, and decisions from phase discussion.
 

package/get-shit-done/templates/roadmap.md

@@ -38,6 +38,7 @@ Decimal phases appear between their surrounding integers in numeric order.
 ### Phase 1: [Name]
 **Goal**: [What this phase delivers]
 **Depends on**: Nothing (first phase)
+**Requirements**: [REQ-01, REQ-02, REQ-03]
 **Research**: Unlikely (established patterns)
 **Plans**: [Number of plans, e.g., "3 plans" or "TBD"]
 
@@ -49,6 +50,7 @@ Plans:
 ### Phase 2: [Name]
 **Goal**: [What this phase delivers]
 **Depends on**: Phase 1
+**Requirements**: [REQ-04, REQ-05]
 **Research**: Likely (new integration)
 **Research topics**: [What needs investigating]
 **Plans**: [Number of plans]
@@ -68,6 +70,7 @@ Plans:
 ### Phase 3: [Name]
 **Goal**: [What this phase delivers]
 **Depends on**: Phase 2
+**Requirements**: [REQ-06, REQ-07, REQ-08]
 **Research**: Likely (external API)
 **Research topics**: [What needs investigating]
 **Plans**: [Number of plans]
@@ -79,6 +82,7 @@ Plans:
 ### Phase 4: [Name]
 **Goal**: [What this phase delivers]
 **Depends on**: Phase 3
+**Requirements**: [REQ-09, REQ-10]
 **Research**: Unlikely (internal patterns)
 **Plans**: [Number of plans]
 

package/get-shit-done/workflows/define-requirements.md

@@ -159,32 +159,53 @@ IDs enable traceability from roadmap phases.
 </step>
 
 <step name="summarize">
-Present summary before committing:
+Present the FULL requirements list before committing — not counts, the actual requirements:
 
 ```
-## Requirements Summary
+## v1 Requirements
 
-**v1 Scope:**
-- Authentication: [N] requirements
-- [Category]: [N] requirements
-- [Category]: [N] requirements
-Total: [X] requirements
+### [Category 1]
+- [ ] **[REQ-ID]**: [Full requirement description]
+- [ ] **[REQ-ID]**: [Full requirement description]
+- [ ] **[REQ-ID]**: [Full requirement description]
 
-**v2 (Deferred):**
-- [Category]: [N] requirements
-Total: [Y] requirements
+### [Category 2]
+- [ ] **[REQ-ID]**: [Full requirement description]
+- [ ] **[REQ-ID]**: [Full requirement description]
+
+[... list ALL v1 requirements ...]
+
+---
+
+## v2 (Deferred)
+
+### [Category]
+- [REQ-ID]: [Requirement description]
+- [REQ-ID]: [Requirement description]
+
+[... list ALL v2 requirements ...]
+
+---
+
+## Out of Scope
 
-**Out of Scope:**
 - [Feature]: [reason]
 - [Feature]: [reason]
 
-**Core Value Alignment:** ✓ Covered / ⚠️ Gaps noted
+[... list ALL exclusions ...]
+
+---
+
+**Core Value:** [from PROJECT.md]
+**Alignment:** ✓ Covered / ⚠️ Gaps noted
 
 ---
 
 Does this capture what you're building? (yes / adjust)
 ```
 
+**Critical:** Show every single requirement. The user must see exactly what they're committing to. Counts are useless — list the actual items.
+
 If "adjust": Return to scope_categories or identify_gaps as appropriate.
 </step>
 

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

@@ -1491,7 +1491,7 @@ ROADMAP_FILE=".planning/ROADMAP.md"
 
 - Mark phase complete: status → "Complete"
 - Add completion date
-  </step>
+</step>
 
 <step name="git_commit_metadata">
 Commit execution metadata (SUMMARY + STATE + ROADMAP):
@@ -1506,7 +1506,7 @@ git add .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md
 git add .planning/STATE.md
 ```
 
-**2. Stage roadmap file:**
+**2. Stage roadmap:**
 
 ```bash
 git add .planning/ROADMAP.md

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

@@ -350,12 +350,14 @@ Research complete:
 
 ## ▶ Next Up
 
-**Create roadmap** — using research findings
+**Define requirements** — scope your v1 from research findings
 
-`/gsd:create-roadmap`
+`/gsd:define-requirements`
 
 <sub>`/clear` first → fresh context window</sub>
 
+**Flow:** research-project → **define-requirements** → create-roadmap
+
 ---
 ```
 </step>

package/package.json

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