zcode-delegate

1# ZCode Delegate
2 
3You are the **orchestrator**. This skill lets you hand a bounded coding task to a separate
4**implementer** — the Z.AI ZCode CLI — then review what it produced and land it yourself. You write
5the brief and own the judgment; ZCode does the typing; you verify and commit.
6 
7Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell
8command and read a file. (It is designed for and run on Claude Code; treat other orchestrators as
9designed-for, not yet proven.)
10 
11## When NOT to use this
12 
13- The task is small enough to just do inline — delegation overhead is not worth it.
14- ZCode is not installed, or its CLI has no model provider configured.
15- You want to write the code yourself, or you only need a review.
16 
17## Prerequisites (check once)
18 
191. **ZCode is installed.** The CLI ships **inside the desktop app** — it is not on PATH and not on
20   npm. The relay resolves it in this order: `--zcode-path <file>` or `ZCODE_CLI` first, then PATH,
21   then the installed app bundle. On Linux the app is an AppImage with no fixed install path, so
22   the flag or the environment variable is required there — the relay guesses nothing.
232. **A model provider is configured for the CLI**, with a key it can actually reach. Being signed
24   into the desktop app is *not* enough — see below.
253. You are in (or will point `--cd` at) the target git repository.
26 
27The relay records the CLI version and how it was resolved into `result.json`, so a surprising
28…