skill-wb-exec

wb-exec Delegate bounded implementation work to another CLI agent; keep planning, supervision and review for yourself.

wb-exec is a DeepSeek Harness plugin (skill bundle): the host agent hands coding / refactoring / test-writing subtasks to a headless CLI executor and gets back a structured result plus the real diff.

The default executor is WorkBuddy / CodeBuddy (DeepSeek V4.1 Flash, effort max), pinned on purpose. If you do not have it, switch backends with --executor — codex, claude, aider, or custom (any CLI, via an argument template). Isolation, supervision, structured capture and the out-of-scope check are identical on every backend. ⚠️ Prerequisite. Whichever backend you pick must be installed on the same machine. Without it the plugin installs but the skill cannot do anything: its first step, doctor, reports ok=false and stops. It never installs dependencies or rewrites configuration on its own.

Fits: tasks with a clear boundary that can be finished independently, with an enumerable set of files; using a cheaper executor for volume while the host only plans and reviews; work that deserves an isolated worktree, reviewed by a human before it lands.

Does not fit: exploratory work, requirements still moving, cross-module rewrites, or anything that needs architectural judgement. Keep those in the host.

*Figure 1. Install-time registration, run-time delegation to the executor, and the audit path that returns artifacts to the review gate — drawn as three columns, read left to right: installation, execution, audit. The execution column shows the ordering that matters: dispatch claims the paths from the lock *before* it spawns the CLI executor, and the executor edits only the worktree wt/, bounded by the owned_paths whitelist. The footnote restates that bound and records that a corrupt lock is refused rather than treated as empty.* Features How it works

*Figure 2. One delegation, drawn as a single unidirectional pass: task authoring, path claim, CLI spawn, worktree edit and git diff, with the observable outputs collected alongside. No cycle is drawn on purpose — a failed review does not re-run the same executor, it re-splits into a smaller package, which is the re-split task edge in Figure 1. The host never merges on its own: review is a separate, mandatory step.*

1. The host writes the task package to disk as JSON (goal, owned_paths, acceptance, ...) 2. dispatch (background) or run (foreground) starts the call; Git repositories get a dedicated worktree by default 3. The executor works and emits stream-json events; the supervisor writes a heartbeat every 5 seconds 4. collect parses the structured result and merges in the real diff and the out-of-scope check 5. The host reads the patch and runs the acceptance commands itself before integrating anything. wb-exec never integrates for you Requirements Python 3.10+ (standard library only, no pip install) One supported CLI executor — pick with --executor or WB_EXECUTOR: workbuddy (default): the script probes for a codebuddy executable and for the CLI embedded in a local WorkBuddy install; set WB_CLI to point at one explicitly codex, claude, aider: found on PATH, or via WB_CLI custom: WB_CLI (the executable) plus WB_CLI_ARGV (a JSON array argument template, see below) Git — optional. Used for worktree isolation and diff capture; a non-Git directory degrades to in-place execution On the workbuddy backend, an account or plan that is allowed to use deepseek-v4.1-flash

Check the environment first:

It returns JSON with ok / cli (the resolved entry point) / cli_version / executor / available_executors / git / is_git_repo / state_root. When ok=false or cli_error is non-empty, stop and hand the raw output to the user — do not install anything or change configuration. Install

This repository is a DSH plugin package (package.json declares dsh.bundle). Once installed, a ctx.skills provider publishes skills/wb-exec/ as a skill.