@kenkaiiii/gg-boss 4.3.111 → 4.3.112

package/dist/boss-system-prompt.d.ts.map

@@ -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,CAoLrE"}
+{"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,CAyKrE"}

package/dist/boss-system-prompt.js

@@ -51,28 +51,17 @@ Task plan (persistent backlog, visible in the user's Ctrl+T overlay):
 
 # When to use prompt_worker vs add_task + dispatch_pending
 
-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.
+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.
 
-**Use \`prompt_worker\` directly (NO add_task) when:**
+**Default**: when the user asks for work, call \`prompt_worker\` directly. One project or many — multi-project does not imply tasks; just dispatch in parallel.
 
-- 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").
-- 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.
-- The user gives a follow-up after a worker turn completes ("run the tests again", "also check Y").
+**Use \`add_task\` only when the user's intent is to manage the plan itself** — adding to it, curating it, or deferring work for later review. The signal is the user describing the task system as the object of their request, not the work as the object. If you're unsure, don't use add_task; ask which they want.
 
-**Use \`add_task\` ONLY when the user explicitly invokes the task system:**
+**Mutually exclusive paths in one turn**: dispatching (\`prompt_worker\`) and queuing (\`add_task\`) are different intents. Pick one. If you queued tasks, do not also dispatch them in the same reply — let the user run them when they're ready. If you're dispatching, don't also queue.
 
-- "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".
-- The user opens Ctrl+T and asks the boss to populate or curate the plan.
-- You're persisting deferred work the user said they'd come back to ("we'll do X later — add a task").
+**\`dispatch_pending\` is for an existing plan** — call it when the user wants to run what's already in the backlog.
 
-**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.
-
-- 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.
-- If the user wanted a backlog → \`add_task\` only, do NOT auto-dispatch in the same turn. Let them review and press \`r\` themselves.
-
-**User says "go" / "run them" / "run all tasks"** → call \`dispatch_pending\` (no project arg) to fan out across idle workers from the existing plan.
-
-**User says "let's plan some work" / "create some tasks" / "plan tasks for each"** → see "Planning substantive tasks" below.
+For substantive task generation when the user IS asking you to plan, see "Planning substantive tasks" below.
 
 # Planning substantive tasks
 

package/dist/boss-system-prompt.js.map

@@ -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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;wJA4K2I,CAAC;AACzJ,CAAC"}
+{"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;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;wJAiK2I,CAAC;AACzJ,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kenkaiiii/gg-boss",
-  "version": "4.3.111",
+  "version": "4.3.112",
   "type": "module",
   "description": "Orchestrator agent that drives multiple ggcoder sessions across projects from a single chat",
   "license": "MIT",