@kenkaiiii/gg-boss 4.3.110 → 4.3.111

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.
@@ -1 +1 @@
1
- {"version":3,"file":"boss-system-prompt.d.ts","sourceRoot":"","sources":["../src/boss-system-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,YAAY,CAAC;AAE9C,wBAAgB,qBAAqB,CAAC,QAAQ,EAAE,WAAW,EAAE,GAAG,MAAM,CAkKrE"}
1
+ {"version":3,"file":"boss-system-prompt.d.ts","sourceRoot":"","sources":["../src/boss-system-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,YAAY,CAAC;AAE9C,wBAAgB,qBAAqB,CAAC,QAAQ,EAAE,WAAW,EAAE,GAAG,MAAM,CAoLrE"}
@@ -51,10 +51,28 @@ Task plan (persistent backlog, visible in the user's Ctrl+T overlay):
51
51
 
52
52
  # When to use prompt_worker vs add_task + dispatch_pending
53
53
 
54
- - **Single ad-hoc instruction** ("answer a question", "do this one quick thing") \`prompt_worker\` directly. No need for the task system.
55
- - **Planning multiple things, especially across projects** → use \`add_task\` to build the plan, then \`dispatch_pending\` to execute. The plan persists across sessions and shows up in the user's overlay.
56
- - **User says "let's plan some work" / "create some tasks" / "plan tasks for each"** → see "Planning substantive tasks" below.
57
- - **User says "go" / "run them"** → call \`dispatch_pending\` (no project arg) to fan out across idle workers.
54
+ The task system is for **backlog management** work the user wants tracked, paused, reviewed in the Ctrl+T overlay, and resumed later. It is **NOT** a wrapper around every dispatch. Default to \`prompt_worker\` (direct, ephemeral) for actual work; reach for \`add_task\` only when the user is clearly managing a queue.
55
+
56
+ **Use \`prompt_worker\` directly (NO add_task) when:**
57
+
58
+ - The user asks for work to happen ("update deps for all projects", "fix the failing tests in X", "audit the auth flow", "read the README and tell me what it does").
59
+ - It's a question or instruction, regardless of whether it touches one project or many. Multi-project does NOT imply tasks. Just call \`prompt_worker\` once per project, in parallel.
60
+ - The user gives a follow-up after a worker turn completes ("run the tests again", "also check Y").
61
+
62
+ **Use \`add_task\` ONLY when the user explicitly invokes the task system:**
63
+
64
+ - "Plan some tasks", "create tasks for each", "add a task to do X", "queue this up", "build me a backlog", "let's plan some work".
65
+ - The user opens Ctrl+T and asks the boss to populate or curate the plan.
66
+ - You're persisting deferred work the user said they'd come back to ("we'll do X later — add a task").
67
+
68
+ **Never do all three of: add_task → tell user to press Ctrl+T → dispatch anyway.** That's the worst of both worlds — you've created a task they didn't ask for, sent them a keybind hint they don't need, AND done the work yourself. Pick one path.
69
+
70
+ - If you're going to do it now → \`prompt_worker\` only, no task. The Ctrl+T hint won't fire because no add_task ran.
71
+ - If the user wanted a backlog → \`add_task\` only, do NOT auto-dispatch in the same turn. Let them review and press \`r\` themselves.
72
+
73
+ **User says "go" / "run them" / "run all tasks"** → call \`dispatch_pending\` (no project arg) to fan out across idle workers from the existing plan.
74
+
75
+ **User says "let's plan some work" / "create some tasks" / "plan tasks for each"** → see "Planning substantive tasks" below.
58
76
 
59
77
  # Planning substantive tasks
60
78
 
@@ -1 +1 @@
1
- {"version":3,"file":"boss-system-prompt.js","sourceRoot":"","sources":["../src/boss-system-prompt.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,qBAAqB,CAAC,QAAuB;IAC3D,MAAM,WAAW,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,CAAC,IAAI,OAAO,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAE/E,OAAO;;;;EAIP,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;wJA0J2I,CAAC;AACzJ,CAAC"}
1
+ {"version":3,"file":"boss-system-prompt.js","sourceRoot":"","sources":["../src/boss-system-prompt.ts"],"names":[],"mappings":"AAEA,MAAM,UAAU,qBAAqB,CAAC,QAAuB;IAC3D,MAAM,WAAW,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,CAAC,IAAI,OAAO,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAE/E,OAAO;;;;EAIP,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;wJA4K2I,CAAC;AACzJ,CAAC"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kenkaiiii/gg-boss",
3
- "version": "4.3.110",
3
+ "version": "4.3.111",
4
4
  "type": "module",
5
5
  "description": "Orchestrator agent that drives multiple ggcoder sessions across projects from a single chat",
6
6
  "license": "MIT",
@@ -27,8 +27,8 @@
27
27
  "react": "^19.2.5",
28
28
  "zod": "^4.4.3",
29
29
  "@kenkaiiii/gg-agent": "4.3.96",
30
- "@kenkaiiii/ggcoder": "4.3.99",
31
- "@kenkaiiii/gg-ai": "4.3.96"
30
+ "@kenkaiiii/gg-ai": "4.3.96",
31
+ "@kenkaiiii/ggcoder": "4.3.99"
32
32
  },
33
33
  "devDependencies": {
34
34
  "@types/node": "^25.6.0",