@jabworks/condux 0.10.2 → 0.11.0

package/index.js

@@ -13,6 +13,14 @@
 // separate `npx skills add` step for condux. This works because the config hook
 // mutates the cached config before OpenCode lazily discovers skills.
 //
+// It also pushes workflow's routing.md onto config.instructions, giving
+// OpenCode the same `/workflow`-as-entry-point enforcement Claude Code and
+// Codex get from their SessionStart hook — OpenCode has no hook system for
+// that, so `instructions` (ambient every turn, verified via `opencode debug
+// config` against a config-hook mutation) is the closest equivalent. Costs
+// ~390 tokens/turn, permanently; that trade was made deliberately, not by
+// default (docket #38).
+//
 // Optional plan-review listener (CONDUX_PLAN_REVIEW=1): when the primary
 // `plan` agent finishes a turn (session.idle), spawns the plan-review annotate
 // server from an installed condux skill tree. Best-effort only — OpenCode does
@@ -28,6 +36,7 @@ import { fileURLToPath } from 'node:url';
 const PKG_DIR = path.dirname(fileURLToPath(import.meta.url));
 const AGENTS_DIR = path.join(PKG_DIR, 'agents');
 const SKILLS_DIR = path.join(PKG_DIR, 'skills');
+const ROUTING_MD = path.join(SKILLS_DIR, 'workflow', 'hooks', 'routing.md');
 
 // Bundled agent files use exactly the frontmatter the toolkit generator emits:
 // a JSON-quoted `description`, a plain `mode`, an optional `permission` deny map
@@ -107,6 +116,13 @@ export const ConduxPlugin = async ({ worktree }) => {
         cfg.skills.paths ??= [];
         if (!cfg.skills.paths.includes(SKILLS_DIR)) cfg.skills.paths.push(SKILLS_DIR);
       }
+
+      // Route through /workflow the same way Claude Code and Codex do —
+      // see the file-header comment for why `instructions` is the mechanism.
+      if (existsSync(ROUTING_MD)) {
+        cfg.instructions ??= [];
+        if (!cfg.instructions.includes(ROUTING_MD)) cfg.instructions.push(ROUTING_MD);
+      }
     },
 
     'chat.params': async (input) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.10.2",
+  "version": "0.11.0",
   "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/condux-doctor/doctor.mjs

@@ -333,7 +333,17 @@ function probeOpencode(hosts) {
     return { host: 'opencode', status: 'broken', detail: 'the installed package entry point does not parse', fix: `reinstall ${PACKAGE}` };
   }
 
-  return { host: 'opencode', status: 'done', detail: 'registered, and the installed package ships its agents and skills' };
+  const routing = path.join(pkg, 'skills', 'workflow', 'hooks', 'routing.md');
+  if (!fs.existsSync(routing)) {
+    return {
+      host: 'opencode',
+      status: 'broken',
+      detail: 'the installed package ships no workflow/hooks/routing.md — /workflow routing enforcement is missing',
+      fix: `reinstall ${PACKAGE}`,
+    };
+  }
+
+  return { host: 'opencode', status: 'done', detail: 'registered, and the installed package ships its agents, skills, and /workflow routing enforcement' };
 }
 
 // The four specialist agents are plugin-level and reached by their own sync

package/skills/root-cause-analysis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: root-cause-analysis
-description: "Enforces root-cause-first bug investigation — read the error, reproduce it, trace the data flow backward. Never propose a solution before the investigation phase completes. Trigger the moment debugging starts — never proactively — and always before any fix is proposed or any change is made. Phrases include \"why is this failing\", \"this bug\", \"unexpected behavior\", \"error when I…\". Not for a jabworks/agentic-toolkit skill or plugin misbehaving (won't trigger, won't show up, dist drift); that's toolkit-debugging-playbook."
+description: "Enforces root-cause-first bug investigation — read the error, reproduce it, trace the data flow backward. Never propose a solution before the investigation phase completes. Trigger the moment debugging starts — never proactively — and always before any fix is proposed or any change is made. Phrases include \"why is this failing\", \"this bug\", \"unexpected behavior\", \"error when I…\", and declarative bug reports with no question mark — \"checkout crashes on empty cart\", \"there's a bug where X happens\" — a stated symptom is a bug report too. Not for a jabworks/agentic-toolkit skill or plugin misbehaving (won't trigger, won't show up, dist drift); that's toolkit-debugging-playbook."
 argument-hint: "<error message or bug description>"
 effort: high
 ---

package/skills/subagent-execution/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: subagent-execution
-description: "Execute a plan using named specialist agents. Default is to implement yourself — only spawn when there is a concrete justification. Trigger when implementing a LARGE plan with tasks that benefit from agent specialization or parallel exploration — including task briefs, review packages, spawn rules, and resuming an interrupted plan from the `.condux/progress/` ledger (not session-handoff). Not for ad-hoc independent tasks outside a plan (that's subagent-deployment)."
+description: "Execute a plan using named specialist agents. Default is to implement yourself — only spawn when there is a concrete justification. Trigger when implementing a LARGE plan with tasks that benefit from agent specialization or parallel exploration — including task briefs, review packages, spawn rules, which model a dispatched agent should get, and resuming an interrupted plan from the `.condux/progress/` ledger (not session-handoff). Not for ad-hoc independent tasks outside a plan (that's subagent-deployment)."
 argument-hint: "<plan file path>"
 ---
 

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

@@ -11,7 +11,7 @@
   { "query": "continue the wave, tasks 5 and 6 are unblocked", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "we compacted mid-plan, where were we with the agents", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "dont re-dispatch tasks that are already done", "should_trigger": true, "expected_skill": "subagent-execution" },
-  { "query": "sdd the plan", "should_trigger": true, "expected_skill": "subagent-execution" },
+  { "query": "spawn the agents for this plan", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "dispatch these three unrelated fixes in parallel", "should_trigger": true, "expected_skill": "subagent-deployment" },
   { "query": "fan out independent lookups across agents", "should_trigger": true, "expected_skill": "subagent-deployment" },
   { "query": "three independent bugs, fix them concurrently", "should_trigger": true, "expected_skill": "subagent-deployment" },