get-shit-done-cc 1.4.3 → 1.4.4

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.
Files changed (2) hide show
  1. package/get-shit-done/workflows/debug.md +35 -15
  2. package/package.json +1 -1
package/get-shit-done/workflows/debug.md CHANGED
@@ -42,26 +42,46 @@ Ask about experience. Investigate the cause yourself.
42
42
  ls .planning/debug/*.md 2>/dev/null | grep -v resolved
43
43
  ```
44
44
 
45
- **If active sessions exist:**
45
+ **If active sessions exist AND no $ARGUMENTS provided:**
46
46
 
47
- Read each file's frontmatter to check status.
47
+ Read each file's frontmatter (status, trigger) and Current Focus (hypothesis, next_action).
48
48
 
49
- If status is NOT "resolved":
49
+ Display inline:
50
50
 
51
- Use AskUserQuestion:
52
- - header: "Resume?"
53
- - question: "Active debug session found. Continue or start new?"
54
- - options:
55
- - "Resume [slug]" - Continue where we left off
56
- - "Start new" - This is a different issue
57
- - "Show status" - Show me current state first
51
+ ```
52
+ ## Active Debug Sessions
53
+
54
+ | # | Slug | Status | Hypothesis | Next Action |
55
+ |---|------|--------|------------|-------------|
56
+ | 1 | auth-logout | investigating | Token refresh not called | Check console output |
57
+ | 2 | api-timeout | gathering | - | Gather symptoms |
58
+ | 3 | cart-bug | fixing | Null reference in context | Apply fix |
59
+
60
+ Reply with a number to resume, or describe a new issue to start fresh.
61
+ ```
62
+
63
+ Wait for user response.
64
+
65
+ - If user replies with number (1, 2, 3) → Load that file, go to `resume_from_file`
66
+ - If user replies with text → Treat as new issue trigger, go to `create_debug_file`
67
+
68
+ **If active sessions exist AND $ARGUMENTS provided:**
69
+
70
+ User wants to start a new debug session. Continue to `create_debug_file`.
71
+
72
+ **If no active sessions AND no $ARGUMENTS:**
73
+
74
+ ```
75
+ No active debug sessions.
76
+
77
+ Describe the issue to start debugging.
78
+ ```
79
+
80
+ Wait for user to describe the issue, then use their response as the trigger.
58
81
 
59
- If "Resume": Load file, go to `resume_from_file`
60
- If "Start new": Continue to `create_debug_file`
61
- If "Show status": Display Current Focus and Symptoms, ask again
82
+ **If no active sessions AND $ARGUMENTS provided:**
62
83
 
63
- **If no active sessions:**
64
- Continue to `create_debug_file`
84
+ Continue to `create_debug_file` with $ARGUMENTS as trigger.
65
85
  </step>
66
86
 
67
87
  <step name="create_debug_file">
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "get-shit-done-cc",
3
- "version": "1.4.3",
3
+ "version": "1.4.4",
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"