delegate-setup

1# Delegate Setup
2 
3You are the **orchestrator** in **setup mode**. Discover installed implementer CLIs, propose a
4**fleet of lanes**, and write configuration only after the user approves.
5 
6This skill does **not** dispatch coding work. It only authors the lane map.
7 
8One concept: **lanes**. Never say “routes.”
9 
10Example lane: **feature** → implementer `opencode`, model `opencode/grok`, variant `high`
11(OpenCode uses `variant` for reasoning intensity, not `effort`).
12 
13## When NOT to use this
14 
15- The user wants a task implemented — use the matching `*-delegate` skill instead.
16- A one-off model change on a single dispatch — pass `--model` / `--effort` / `--variant` on that relay.
17 
18## Hard rules
19 
201. Every lane **must** include `implementer`.
212. Put dials on the same object (`model`, `effort` or `variant`, …) only if that implementer supports them — see [references/schema.md](references/schema.md).
223. Show a human-readable lane table **and** the full JSON before every write; re-show after every tweak.
234. Write **only** after an explicit approval (“yes”, “approve”, “write it”).
245. Ask scope unless already clear: **global** (all projects) vs **this repo only**. Never create a project file just because cwd is a git repo. If there is no git repo, default to global and say so.
256. Do not invent model identifiers.
267. In interview or usage-scan mode, never write **any** dial the user did not give you and the schema does not require — omit it, so the CLI’s or relay’s own default applies.
27…