opencode-delegate
Delegate a coding task to the OpenCode CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to OpenCode — phrasings like "have OpenCode do X", "delegate this to OpenCode", "run it through OpenCode", or "use OpenCode to implement/fix/refactor" — or wants to run a queue of coding tasks through OpenCode while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating
npx skills add amElnagdy/delegate-skills --skill opencode-delegate --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OpenCode Delegate You are the **orchestrator**. This skill lets you hand a bounded coding task to a separate **implementer** — the OpenCode CLI — then review what it produced and land it yourself. You write the brief and own the judgment; OpenCode does the typing in its own session; you verify and commit. Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell command and read a file, so any agent with those two capabilities — Claude Code, OpenCode driving a sibling session, or a comparable one — can drive it. (It is designed for and run on Claude Code; treat other orchestrators as designed-for, not yet proven.) ## When NOT to use this - The task is small enough to just do inline — delegation overhead is not worth it. - The `opencode` CLI is not installed or not authenticated (run `opencode auth login`). - You want to write the code yourself, or you only need a review (use the `plan` agent via `--read-only`). ## Prerequisites (check once) 1. `opencode --version` succeeds. If not, install (`npm i -g opencode-ai`, or the native installer from opencode.ai) and `opencode auth login`. 2. **Confirm which `opencode` is on PATH.** `command -v o
- When NOT to use this
- Prerequisites (check once)
- Choose the implementer model
- The loop
- 1. Write the brief
- 2. Dispatch
- 3. Wait for completion
- 4. Review — do not trust the self-report
- 5. Land it
- Autonomy model
- Authorization model
- References
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --model <provider/model> --cd /path/to/repo fleet lane from delegate-setup: add --lane <name> (dials apply; flags still win) read-only (review/diagnosis, no edits): add --read-only (uses the plan agent) continue the previous OpenCode session: add --resume-last (delta brief only; keeps the model) hard time limit (watchdog): add --timeout 2h (default: off; implementation runs routinely need 1-2h) see all options: node .../relay.mjs --help
What does the opencode-delegate skill do?
Delegate a coding task to the OpenCode CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to OpenCode — phrasings like "have OpenCode do X", "delegate this to OpenCode", "run it through OpenCode", or "use OpenCode to implement/fix/refactor" — or wants to run a queue of coding tasks through OpenCode while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating
How do I install it?
Run `npx skills add amElnagdy/delegate-skills --skill opencode-delegate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From amElnagdy/delegate-skills, a repository with 684 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.