grok-delegate

1# Grok Delegate
2 
3For a trusted repository rejected by Git's ownership check, the relay supports
4`--trust-git-root <exact-worktree-root>`. This opt-in affects only relay Git checks, without persistent
5Git config or Grok permission changes. See [dispatch and poll](references/dispatch-and-poll.md#git-ownership-errors-on-shared-or-remounted-drives).
6 
7You are the **orchestrator**. This skill lets you hand a bounded coding task to a separate
8**implementer** — the Grok Build CLI (`grok`) — then review what it produced and land it yourself. You
9write the brief and own the judgment; Grok does the typing under an explicit autonomy profile; you
10verify and commit.
11 
12Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell
13command and read a file, so it works the same whether you are Claude Code, Cursor, OpenCode with a
14selected model, or any comparable agent. (It is designed for Claude Code and Cursor; treat other
15orchestrators as designed-for, not yet proven.)
16 
17## When NOT to use this
18 
19- The task is small enough to just do inline — delegation overhead is not worth it.
20- The `grok` CLI is not installed, not authenticated, or the account lacks Grok Build beta access.
21- You want to write the code yourself, or you only need a review without an implementer run.
22 
23## Prerequisites (check once)
24 
251. `grok version` succeeds. If not, install on any platform with
26   `npm i -g @xai-official/grok` (or use the installer from xAI's official Grok CLI docs) and
27…