Delegate Setup
Configure delegation fleet lanes: which implementer CLI handles which kind of work...
Install
npx skills add amElnagdy/delegate-skills --skill delegate-setup -g -a claude-code -y- Repository
- amElnagdy/delegate-skills2.5k
- Category
- Design
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 2,526 tokens
- Runs scripts
- Yes, review before use
What it does
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.
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
*-delegateskill instead. - A one-off model change on a single dispatch, pass
--model/--effort/--varianton that relay.
Hard rules
- Every lane must include
implementer. - Put dials on the same object (
model,effortorvariant, …) only if that implementer supports them, see references/schema.md. - Show a human-readable lane table and the full JSON before every write; re-show after every tweak.
- Write only after an explicit approval (“yes”, “approve”, “write it”).
- 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.
- Do not invent model identifiers.
- 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.
- Prefer 3, 5 useful lanes over a kitchen-sink map.
- Never edit
AGENTS.md,CLAUDE.md, or other user agent-instruction files. - Never run a
*-delegaterelay 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
node "<skill-dir>/scripts/discover.mjs"
