get-shit-done-cc 1.1.0 → 1.1.2

package/README.md

@@ -38,13 +38,17 @@ That's what this is. No enterprise roleplay bullshit. Just an incredibly effecti
 /gsd:new-project
 ```
 
-The system asks questions. Keeps asking until it has everything — your goals, constraints, tech preferences, edge cases. You go back and forth until the idea is fully captured.
+The system asks questions. Keeps asking until it has everything — your goals, constraints, tech preferences, edge cases. You go back and forth until the idea is fully captured. Creates **PROJECT.md**.
 
-### 2. Initialize the project
+### 2. Research (optional) and create roadmap
 
-Your idea becomes:
+```
+/gsd:research-project   # For niche domains (3D, audio, shaders)
+/gsd:create-roadmap     # Create phases and state tracking
+```
+
+For complex domains, research spawns subagents to discover ecosystem patterns before planning. Then roadmap creation produces:
 
-- **PROJECT.md** - Project vision (~50 lines)
 - **ROADMAP.md** - Phases from start to finish
 - **STATE.md** - Living memory that persists across sessions
 
@@ -139,7 +143,9 @@ You're never locked in. The system adapts.
 
 | Command                           | What it does                                                  |
 | --------------------------------- | ------------------------------------------------------------- |
-| `/gsd:new-project`                | Extract your idea through questions, create project structure |
+| `/gsd:new-project`                | Extract your idea through questions, create PROJECT.md        |
+| `/gsd:research-project`           | Research domain ecosystem before roadmap (optional)           |
+| `/gsd:create-roadmap`             | Create roadmap and state tracking                             |
 | `/gsd:plan-phase [N]`             | Generate task plans for phase                                 |
 | `/gsd:execute-plan`               | Run plan via subagent                                         |
 | `/gsd:progress`                   | Where am I? What's next?                                      |
@@ -149,6 +155,7 @@ You're never locked in. The system adapts.
 | `/gsd:add-phase`                  | Append phase to roadmap                                       |
 | `/gsd:insert-phase [N]`           | Insert urgent work                                            |
 | `/gsd:discuss-phase [N]`          | Gather context before planning                                |
+| `/gsd:research-phase [N]`         | Deep ecosystem research for niche domains                     |
 | `/gsd:list-phase-assumptions [N]` | See what Claude thinks before you correct it                  |
 | `/gsd:pause-work`                 | Create handoff file when stopping mid-phase                   |
 | `/gsd:resume-work`                | Restore from last session                                     |

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

@@ -507,31 +507,27 @@ See ~/.claude/get-shit-done/references/scope-estimation.md for complete splittin
 </step>
 
 <step name="confirm_breakdown">
-**Check workflow config for gate behavior:**
+**FIRST: Check if confirmation gate is disabled**
 
 ```bash
 cat .planning/config.json 2>/dev/null
 ```
 
-Parse the config:
-
-- If `mode: "yolo"` → auto-approve
-- If `mode: "interactive"` → prompt user
-- If `mode: "custom"` → check `gates.confirm_breakdown`
-
-**If auto-approved:**
+**If `mode: "yolo"`** → Show summary below, then SKIP directly to write_phase_prompt step. Do NOT ask questions. Do NOT wait for confirmation.
 
 ```
 ⚡ Auto-approved: Phase [X] breakdown ([N] tasks, [M] plan(s))
 
-[Show breakdown summary without prompting]
+[Brief breakdown summary - task names and types only]
 
 Proceeding to plan creation...
 ```
 
-**If prompting (interactive mode or custom with gate enabled):**
+---
 
-Present the breakdown inline:
+**Only if mode is "interactive" OR (mode is "custom" AND gates.confirm_breakdown is true), continue below:**
+
+Present the breakdown inline and wait for confirmation:
 
 **If single plan (2-3 tasks):**
 
@@ -553,7 +549,7 @@ Does this breakdown look right? (yes / adjust / start over)
 ```
 Here's the proposed breakdown for Phase [X]:
 
-This phase requires 3 plans to maintain quality:
+This phase requires [N] plans to maintain quality:
 
 ### Plan 1: {phase}-01-PLAN.md - [Subsystem/Component Name]
 1. [Task name] - [brief description] [type]
@@ -564,9 +560,7 @@ This phase requires 3 plans to maintain quality:
 1. [Task name] - [brief description] [type]
 2. [Task name] - [brief description] [type]
 
-### Plan 3: {phase}-03-PLAN.md - [Subsystem/Component Name]
-1. [Task name] - [brief description] [type]
-2. [Task name] - [brief description] [type]
+[Additional plans as needed...]
 
 Each plan is independently executable and scoped to ~50% context.
 
@@ -595,25 +589,17 @@ Only ask if genuinely ambiguous. Don't ask obvious choices.
 </step>
 
 <step name="decision_gate">
-After breakdown confirmed (or auto-approved):
-
-**Check workflow config for gate behavior:**
-
-Read config from previous step (already parsed).
+**FIRST: Check mode from config (already parsed in confirm_breakdown)**
 
-- If `mode: "yolo"` → auto-approve
-- If `mode: "interactive"` → prompt user
-- If `mode: "custom"` → check `gates.confirm_plan`
-
-**If auto-approved:**
+**If `mode: "yolo"`** → Output the message below, then SKIP directly to write_phase_prompt. Do NOT ask questions.
 
 ```
 ⚡ Auto-approved: Create phase prompt for Phase [X]
 ```
 
-Proceed directly to write_phase_prompt.
+---
 
-**If prompting:**
+**Only if mode is "interactive" OR (mode is "custom" AND gates.confirm_plan is true), continue below:**
 
 Use AskUserQuestion:
 

package/package.json

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