get-shit-done-cc 1.4.8 → 1.4.9

package/commands/gsd/discuss-phase.md

@@ -7,7 +7,7 @@ argument-hint: "[phase]"
 <objective>
 Help the user articulate their vision for a phase through collaborative thinking.
 
-Purpose: Understand HOW the user imagines this phase working — what it looks like, what's essential, what's out of scope. You're a thinking partner helping them crystallize their vision, not an interviewer gathering technical requirements.
+Purpose: Understand HOW the user imagines this phase working — what it looks like, what's essential. You're a thinking partner helping them crystallize their vision, not an interviewer gathering technical requirements.
 
 Output: {phase}-CONTEXT.md capturing the user's vision for the phase
 </objective>
@@ -36,7 +36,6 @@ Phase number: $ARGUMENTS (required)
    - Use AskUserQuestion: "How do you imagine this working?" with interpretation options
    - Use AskUserQuestion to follow their thread — probe what excites them
    - Use AskUserQuestion to sharpen the core — what's essential for THIS phase
-   - Use AskUserQuestion to find boundaries — what's explicitly out of scope
    - Use AskUserQuestion for decision gate (ready / ask more / let me add context)
    - Create CONTEXT.md capturing their vision
 5. Offer next steps (research or plan the phase)
@@ -55,6 +54,6 @@ User is the visionary, you are the builder:
 
 - Phase validated against roadmap
 - Vision gathered through collaborative thinking (not interrogation)
-- CONTEXT.md captures: how it works, what's essential, what's out of scope
+- CONTEXT.md captures: how it works, what's essential
 - User knows next steps (research or plan the phase)
 </success_criteria>

package/commands/gsd/execute-phase.md

@@ -24,11 +24,7 @@ Context budget: ~15% orchestrator, 100% fresh per subagent.
 
 <execution_context>
 @~/.claude/get-shit-done/workflows/execute-phase.md
-@~/.claude/get-shit-done/workflows/execute-plan.md
 @~/.claude/get-shit-done/templates/subagent-task-prompt.md
-@~/.claude/get-shit-done/templates/summary.md
-@~/.claude/get-shit-done/references/checkpoints.md
-@~/.claude/get-shit-done/references/tdd.md
 </execution_context>
 
 <context>

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

@@ -32,17 +32,6 @@ Template for `.planning/phases/XX-name/{phase}-CONTEXT.md` - captures the user's
 
 </essential>
 
-<boundaries>
-## What's Out of Scope
-
-[Explicit exclusions for this phase. What are we NOT building? Where does this phase end and the next begin?]
-
-- [Not doing X - that's Phase Y]
-- [Not including Z - deferred]
-- [Explicitly excluding W]
-
-</boundaries>
-
 <specifics>
 ## Specific Ideas
 
@@ -91,16 +80,6 @@ The main thing is seeing their active projects and what needs attention. Think o
 
 </essential>
 
-<boundaries>
-## What's Out of Scope
-
-- Team features (shared dashboards, permissions) - that's a future milestone
-- Analytics/reporting - just show what needs attention, not graphs
-- Customizable layouts - keep it simple, one good layout
-- Mobile optimization - desktop first for now
-
-</boundaries>
-
 <specifics>
 ## Specific Ideas
 

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

@@ -119,14 +119,7 @@ Use AskUserQuestion:
 - question: "What's the most important part of this phase?"
 - options: Key aspects they've mentioned + "All equally important" + "Something else"
 
-**4. Find boundaries:**
-
-Use AskUserQuestion:
-- header: "Scope"
-- question: "What's explicitly out of scope for this phase?"
-- options: Things that might be tempting + "Nothing specific" + "Let me list them"
-
-**5. Capture specifics (optional):**
+**4. Capture specifics (optional):**
 
 If they seem to have specific ideas, use AskUserQuestion:
 - header: "Specifics"
@@ -138,8 +131,9 @@ CRITICAL — What NOT to ask:
 - Codebase patterns (you read the code)
 - Success metrics (too corporate)
 - Constraints they didn't mention (don't interrogate)
+- What's out of scope (implicit from roadmap)
 
-**6. Decision gate:**
+**5. Decision gate:**
 
 Use AskUserQuestion:
 - header: "Ready?"
@@ -170,7 +164,6 @@ Populate template sections with VISION context (not technical analysis):
 
 - `<vision>`: How the user imagines this working
 - `<essential>`: What must be nailed in this phase
-- `<boundaries>`: What's explicitly out of scope
 - `<specifics>`: Any particular look/feel/behavior mentioned
 - `<notes>`: Any other context gathered
 
@@ -191,9 +184,6 @@ Created: .planning/phases/${PHASE}-${SLUG}/${PHASE}-CONTEXT.md
 ## Essential
 [What must be nailed]
 
-## Boundaries
-[What's out of scope]
-
 ---
 
 ## ▶ Next Up
@@ -240,7 +230,7 @@ Confirm: "Committed: docs(${PHASE}): capture phase context"
 
 - Phase validated against roadmap
 - Vision gathered through collaborative thinking (not interrogation)
-- User's imagination captured: how it works, what's essential, what's out of scope
+- User's imagination captured: how it works, what's essential
 - CONTEXT.md created in phase directory
 - CONTEXT.md committed to git
 - User knows next steps (typically: research or plan the phase)

package/package.json

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