agent-conveyor 0.1.20 → 0.1.21

package/README.md

@@ -168,8 +168,8 @@ conveyor plugin-status
 
 The per-project default ledger for operator sessions is
 `.codex-workers/workerctl.db`. The initial included skills are
-`conveyor-create-pair`, `conveyor-create-worker-set`, and
-`conveyor-check-status`.
+`conveyor-create-pair`, `conveyor-create-worker-set`,
+`conveyor-check-status`, and `conveyor-whats-next-nudger`.
 
 After install, the intended Codex app entry point is natural language. Open a
 new Codex app session in the target repo and say:
@@ -204,6 +204,9 @@ print `CONVEYOR POLL`, `CONVEYOR RECEIVED`, `WORK`, `CONVEYOR SEND`, and
 audit proof, not a replacement for the live session story. Idle polls may be a
 single `CONVEYOR IDLE` line.
 
+For bounded follow-up passes after the first worker result, use
+`Use the conveyor-whats-next-nudger skill`.
+
 Dispatch is core infrastructure for supervised worker/manager pairs. The
 `pair` workflow starts a detached Dispatch watch process by default so worker
 completion is routed to the bound manager mechanically. For manually bound

package/dist/cli/typescript-runtime.js

@@ -6697,7 +6697,12 @@ function runInstallSkillsCommand(parsed, options) {
     return { exitCode: 0, handled: true, stdout: `${lines.join("\n")}\n` };
 }
 const AGENT_CONVEYOR_PLUGIN_NAME = "agent-conveyor";
-const AGENT_CONVEYOR_PLUGIN_SKILLS = ["conveyor-create-pair", "conveyor-create-worker-set", "conveyor-check-status"];
+const AGENT_CONVEYOR_PLUGIN_SKILLS = [
+    "conveyor-create-pair",
+    "conveyor-create-worker-set",
+    "conveyor-check-status",
+    "conveyor-whats-next-nudger",
+];
 function resolveCodexHome(parsed, options) {
     return resolve(expandUserPath(parsed.flags.codexHome ?? options.env?.CODEX_HOME ?? join(homedir(), ".codex")));
 }