@jabworks/condux 0.10.0 → 0.10.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "OpenCode plugin for the condux workflow toolkit — bundles the condux skills and injects the specialist agents (coder, explorer, planner, researcher) plus an opt-in plan-review listener.",
   "type": "module",
   "publishConfig": {

package/skills/subagent-deployment/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: subagent-deployment
-description: "Fan out 2+ independent tasks across named agents (explorer/researcher/planner/coder) in a single message when they share no files and no dependencies. For ad-hoc independent work discovered outside a formal plan. Trigger when two or more genuinely independent tasks are on the table — nothing shared between them, no ordering — and any mix of named agents fits. Not for executing an ordered plan task-by-task (that's subagent-execution)."
+description: "Fan out 2+ independent tasks across named agents (explorer/researcher/planner/coder) in a single message when they share no files and no dependencies. For ad-hoc independent work discovered outside a formal plan. Trigger when the fan-out is already the ask — \"in parallel\", \"fan out\", \"dispatch these together\", \"kick off explorer and researcher\" — over two or more genuinely independent tasks, nothing shared, no ordering. Independence alone is not the signal: a plain implementation request goes to workflow first, which loads this when the tier warrants it. Also owns which agent gets dispatched: asking to spawn a generic or custom-prompt subagent routes here, where the answer is one of the four named agents instead. Not for executing an ordered plan task-by-task (that's subagent-execution)."
 argument-hint: "<list of independent tasks>"
 ---
 
@@ -8,6 +8,12 @@ argument-hint: "<list of independent tasks>"
 
 Deploy independent agents at once, not one at a time. For genuinely unrelated work — not for executing an ordered plan.
 
+**This runs inside `/workflow`, not instead of it.** Independent work is a
+precondition, not a trigger: "fix these three unrelated tests" is an
+implementation request and goes to the router, which loads this skill if the
+tier warrants it. What reaches here directly is a request that already names
+the fan-out — parallel, dispatch, fan out, these agents at once.
+
 ## Usage
 
 ```

package/skills/subagent-deployment/evals/trigger_eval.json

@@ -1,7 +1,7 @@
 [
-  { "query": "fix these 3 unrelated failing test files at once", "should_trigger": true, "expected_skill": "subagent-deployment" },
+  { "query": "fix these 3 unrelated failing test files at once", "should_trigger": true, "expected_skill": "workflow", "note": "cold bug-fix request: the router owns it and loads subagent-deployment only if the tier warrants" },
   { "query": "in parallel: look up the stripe api and explore the auth module", "should_trigger": true, "expected_skill": "subagent-deployment" },
-  { "query": "two independent bugs in different packages, handle both", "should_trigger": true, "expected_skill": "subagent-deployment" },
+  { "query": "two independent bugs in different packages, handle both", "should_trigger": true, "expected_skill": "workflow", "note": "cold bug-fix request: independence alone does not bypass the router" },
   { "query": "fan out this research across agents", "should_trigger": true, "expected_skill": "subagent-deployment" },
   { "query": "batch these lookups together", "should_trigger": true, "expected_skill": "subagent-deployment" },
   { "query": "run these together, theyre totally unrelated", "should_trigger": true, "expected_skill": "subagent-deployment" },
@@ -17,6 +17,6 @@
   { "query": "one small task, just do it yourself", "should_trigger": true, "expected_skill": "workflow" },
   { "query": "deploy the app to production", "should_trigger": false, "expected_skill": null },
   { "query": "set up the deployment pipeline for staging", "should_trigger": false, "expected_skill": null },
-  { "query": "parallelize the test suite in ci", "should_trigger": false, "expected_skill": null },
+  { "query": "parallelize the test suite in ci", "should_trigger": true, "expected_skill": "workflow", "note": "parallelising a test suite is an implementation request, not a fan-out instruction" },
   { "query": "map reduce over these records", "should_trigger": false, "expected_skill": null }
 ]