# Delegate Setup

Configure delegation fleet lanes: which implementer CLI handles which kind of work...

- Repository: https://github.com/amElnagdy/delegate-skills (2546 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add amElnagdy/delegate-skills --skill delegate-setup -g -a claude-code -y`
Codex: `npx skills add amElnagdy/delegate-skills --skill delegate-setup -g -a codex -y`
Cursor: `npx skills add amElnagdy/delegate-skills --skill delegate-setup -g -a cursor -y`
Gemini CLI: `npx skills add amElnagdy/delegate-skills --skill delegate-setup -g -a gemini-cli -y`

## Description

Configure delegation fleet lanes: which implementer CLI handles which kind of work, with optional model and effort (or variant) dials. Discovers installed CLIs, proposes a lane map for user approval, and writes global or project config only after explicit yes. Use when the user asks to set up, configure, or reconfigure delegation lanes, a fleet of lanes, or which implementer handles feature/tests/ui work, not for dispatching a coding task to an implementer.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Delegate Setup

You are the **orchestrator** in **setup mode**. Discover installed implementer CLIs, propose a
**fleet of lanes**, and write configuration only after the user approves.

This skill does **not** dispatch coding work. It only authors the lane map.

One concept: **lanes**. Never say “routes.”

Example lane: **feature** → implementer `opencode`, model `opencode/grok`, variant `high`
(OpenCode uses `variant` for reasoning intensity, not `effort`).

## When NOT to use this

- The user wants a task implemented, use the matching `*-delegate` skill instead.
- A one-off model change on a single dispatch, pass `--model` / `--effort` / `--variant` on that relay.

## Hard rules

1. Every lane **must** include `implementer`.
2. Put dials on the same object (`model`, `effort` or `variant`, …) only if that implementer supports them, see [references/schema.md](references/schema.md).
3. Show a human-readable lane table **and** the full JSON before every write; re-show after every tweak.
4. Write **only** after an explicit approval (“yes”, “approve”, “write it”).
5. 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.
6. Do not invent model identifiers.
7. 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.
8. Prefer 3, 5 useful lanes over a kitchen-sink map.
9. Never edit `AGENTS.md`, `CLAUDE.md`, or other user agent-instruction files.
10. Never run a `*-delegate` relay from this skill.

(`<skill-dir>` is this skill’s install directory, the folder that contains this `SKILL.md`.)

## Flow

`discover → load → grounding menu → propose (with Basis) → scope → approve → write`

### 1. Discover

```bash
node "<skill-dir>/scripts/discover.mjs"
```

The rest: https://github.com/amElnagdy/delegate-skills/blob/HEAD/skills/delegate-setup/SKILL.md