get-shit-done-cc 1.1.1 → 1.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -507,31 +507,27 @@ See ~/.claude/get-shit-done/references/scope-estimation.md for complete splittin
507
507
  </step>
508
508
 
509
509
  <step name="confirm_breakdown">
510
- **Check workflow config for gate behavior:**
510
+ **FIRST: Check if confirmation gate is disabled**
511
511
 
512
512
  ```bash
513
513
  cat .planning/config.json 2>/dev/null
514
514
  ```
515
515
 
516
- Parse the config:
517
-
518
- - If `mode: "yolo"` → auto-approve
519
- - If `mode: "interactive"` → prompt user
520
- - If `mode: "custom"` → check `gates.confirm_breakdown`
521
-
522
- **If auto-approved:**
516
+ **If `mode: "yolo"`** → Show summary below, then SKIP directly to write_phase_prompt step. Do NOT ask questions. Do NOT wait for confirmation.
523
517
 
524
518
  ```
525
519
  ⚡ Auto-approved: Phase [X] breakdown ([N] tasks, [M] plan(s))
526
520
 
527
- [Show breakdown summary without prompting]
521
+ [Brief breakdown summary - task names and types only]
528
522
 
529
523
  Proceeding to plan creation...
530
524
  ```
531
525
 
532
- **If prompting (interactive mode or custom with gate enabled):**
526
+ ---
533
527
 
534
- Present the breakdown inline:
528
+ **Only if mode is "interactive" OR (mode is "custom" AND gates.confirm_breakdown is true), continue below:**
529
+
530
+ Present the breakdown inline and wait for confirmation:
535
531
 
536
532
  **If single plan (2-3 tasks):**
537
533
 
@@ -553,7 +549,7 @@ Does this breakdown look right? (yes / adjust / start over)
553
549
  ```
554
550
  Here's the proposed breakdown for Phase [X]:
555
551
 
556
- This phase requires 3 plans to maintain quality:
552
+ This phase requires [N] plans to maintain quality:
557
553
 
558
554
  ### Plan 1: {phase}-01-PLAN.md - [Subsystem/Component Name]
559
555
  1. [Task name] - [brief description] [type]
@@ -564,9 +560,7 @@ This phase requires 3 plans to maintain quality:
564
560
  1. [Task name] - [brief description] [type]
565
561
  2. [Task name] - [brief description] [type]
566
562
 
567
- ### Plan 3: {phase}-03-PLAN.md - [Subsystem/Component Name]
568
- 1. [Task name] - [brief description] [type]
569
- 2. [Task name] - [brief description] [type]
563
+ [Additional plans as needed...]
570
564
 
571
565
  Each plan is independently executable and scoped to ~50% context.
572
566
 
@@ -595,25 +589,17 @@ Only ask if genuinely ambiguous. Don't ask obvious choices.
595
589
  </step>
596
590
 
597
591
  <step name="decision_gate">
598
- After breakdown confirmed (or auto-approved):
599
-
600
- **Check workflow config for gate behavior:**
601
-
602
- Read config from previous step (already parsed).
592
+ **FIRST: Check mode from config (already parsed in confirm_breakdown)**
603
593
 
604
- - If `mode: "yolo"`auto-approve
605
- - If `mode: "interactive"` → prompt user
606
- - If `mode: "custom"` → check `gates.confirm_plan`
607
-
608
- **If auto-approved:**
594
+ **If `mode: "yolo"`**Output the message below, then SKIP directly to write_phase_prompt. Do NOT ask questions.
609
595
 
610
596
  ```
611
597
  ⚡ Auto-approved: Create phase prompt for Phase [X]
612
598
  ```
613
599
 
614
- Proceed directly to write_phase_prompt.
600
+ ---
615
601
 
616
- **If prompting:**
602
+ **Only if mode is "interactive" OR (mode is "custom" AND gates.confirm_plan is true), continue below:**
617
603
 
618
604
  Use AskUserQuestion:
619
605
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "get-shit-done-cc",
3
- "version": "1.1.1",
3
+ "version": "1.1.2",
4
4
  "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
5
5
  "bin": {
6
6
  "get-shit-done-cc": "bin/install.js"