get-shit-done-cc 1.2.2 → 1.2.3

package/commands/gsd/discuss-milestone.md

@@ -3,9 +3,9 @@ description: Gather context for next milestone through adaptive questioning
 ---
 
 <objective>
-Use adaptive questioning to gather comprehensive milestone context before creating a new milestone.
+Help you figure out what to build in the next milestone through collaborative thinking.
 
-Purpose: After completing a milestone, discuss the scope and focus of the next milestone before diving into phase creation. Builds understanding of goals, constraints, priorities, and lessons learned.
+Purpose: After completing a milestone, explore what features you want to add, improve, or fix. Features first — scope and phases derive from what you want to build.
 Output: Context gathered, then routes to /gsd:new-milestone
 </objective>
 
@@ -28,10 +28,9 @@ Output: Context gathered, then routes to /gsd:new-milestone
 1. Verify previous milestone complete (or acknowledge active milestone)
 2. Present context from previous milestone (accomplishments, phase count)
 3. Follow discuss-milestone.md workflow:
-   - Ask about milestone theme/focus
-   - Ask about scope (estimated phases)
-   - Ask about constraints and priorities
-   - Ask about lessons from previous milestone
+   - Ask: "What do you want to add, improve, or fix?"
+   - Dig into features they mention
+   - Help them articulate what matters most
    - Present decision gate (ready / ask more / let me add context)
 4. Hand off to /gsd:new-milestone with gathered context
 </process>

package/commands/gsd/help.md

@@ -67,11 +67,11 @@ Usage: `/gsd:create-roadmap`
 ### Phase Planning
 
 **`/gsd:discuss-phase <number>`**
-Gather phase context through adaptive questioning before planning.
+Help articulate your vision for a phase before planning.
 
-- Builds understanding of objectives, constraints, risks
-- Creates CONTEXT.md in phase directory
-- Use before planning unfamiliar or complex phases
+- Captures how you imagine this phase working
+- Creates CONTEXT.md with your vision, essentials, and boundaries
+- Use when you have ideas about how something should look/feel
 
 Usage: `/gsd:discuss-phase 2`
 
@@ -86,10 +86,10 @@ Comprehensive ecosystem research for niche/complex domains.
 Usage: `/gsd:research-phase 3`
 
 **`/gsd:list-phase-assumptions <number>`**
-Surface Claude's assumptions about a phase before planning.
+See what Claude is planning to do before it starts.
 
-- Shows what Claude thinks about technical approach, scope, risks
-- Enables early course correction before planning begins
+- Shows Claude's intended approach for a phase
+- Lets you course-correct if Claude misunderstood your vision
 - No files created - conversational output only
 
 Usage: `/gsd:list-phase-assumptions 3`
@@ -141,10 +141,10 @@ Result: Creates Phase 7.1
 ### Milestone Management
 
 **`/gsd:discuss-milestone`**
-Gather context for next milestone through adaptive questioning.
+Figure out what you want to build in the next milestone.
 
-- Reviews previous milestone accomplishments
-- Asks about scope, constraints, priorities for 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`

package/package.json

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