- name
Use when you have a task and must decide WHO does it — yourself, a spawned subagent, or another agent in the topology that already holds the context — or how to brief the agent you hand it to, which d
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill delegating-work -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill delegating-work -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill delegating-work -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mvschwarz/openrig --skill delegating-work -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/mvschwarz/openrig/tree/HEAD/packages/daemon/assets/plugins/openrig-core/skills/delegating-workFrom the publisher
Getting work done well is a context problem. The agent best suited to a task is the one who already holds the context that task requires. Before you spawn a subagent or grind it out yourself, ask who that is.
Ask: how much would a blank slate have to read in before it could do this correctly?
For self-contained work that is fully specifiable in the prompt, spawn a subagent instead of spending your own context: tracing, research, grounding passes, summarizing, scanning log files, searching, fetching, web search, mechanical extraction with citations. This is the common shape and it is under-used.
Subagents start as blank slates, and you cannot anticipate everything they need to know. Give one a task where there is a lot to understand and it will have blind spots it does not know it has — it will complete the task and return a false conclusion, not from weakness but because it lacked the context to know what "correct" even looked like.
This is the unknown-unknowns problem, and it is the single most common subagent failure: a poorly-contextualized summary is worse than no summary, because it arrives looking like an answer. Overreliance on subagents for context-heavy work causes more problems than it solves — and a team burned by it stops using subagents at all, which is the wrong correction. The fix is not "avoid subagents"; it is "match the task to the context it needs."
Before delegating to a blank slate, ask: would a wrong-but-plausible answer here be detectable? If the requester cannot check the result against something they already know — a citation they can open, a count they can re-run — the blind-spot risk is unacceptable, and that task belongs with an agent that holds the context.
file:line citations and an explicit instruction to report facts, not recommendations. Self-contained; the requester can verify the citations.This is really "route work to whoever holds the context," with subagents as the option for work that needs none. The audience is every agent — implementers and QA seats make this call as much as orchestrators do.
How to brief another agent depends on the model it runs, so check before you hand over anything open-ended.
rig ps --nodes --json shows the model each seat's spec declares (model; null if none is declared). A declared
model can differ from the one running, so if it's null, or you aren't sure, ask the seat which model it's running.
Describe the task, not the agent: don't tell a model which group it's in, or call it weaker. A model can take a label like that literally and work down to it. A newer model in a family above (a later Opus, Fable, or Codex Sol or Astra) belongs with the goal-oriented group. A model the lines above can't place, such as a new family or an unfamiliar tier, starts in the second group until you know where it sits; its maker's own description (frontier or workhorse, versus balanced, fast or affordable) is a good first signal.
Whoever does the work, give them the goal, why it matters, the context you hold and where to find more. When you have the requester's own words, pass them on instead of compressing them into a list of steps. A goal-oriented model builds better from that than from a narrow spec, which gets exactly what was written and not what was wanted, so let it decide how; don't pre-do its research or fence what it may conclude. For other models, add the steps and boundaries the work needs, a piece at a time. Keep exact instructions for the few things that must be exact, and say why.
dispatching-parallel-agents (the fan-out mechanics).subagent-driven-development.directing-partner-agents.human-in-the-loop.© 2026 Skills Rack.
---name: delegating-workdescription: Use when you have a task and must decide WHO does it — yourself, a spawned subagent, or another agent in the…---# packages/daemon/assets/plugins/openrig-core/skills/delegating-work/SKILL.mdOverview
Use when you have a task and must decide WHO does it — yourself, a spawned subagent, or another agent in the topology that already holds the context — or how to brief the agent you hand it to, which depends on the model it runs. The rule: how much would a blank slate have to read in to do this correctly? A lot → route to a context-holding agent; a little → subagent; unsure → a real agent or yourself. NOT the mechanics of fanning out (that's dispatching-parallel-agents / subagent-driven-development) — this is the who/whether decision, and the failure mode that makes teams abandon subagents. Also use it to decide how far to trust a delegated result.
FAQ
Download packages/daemon/assets/plugins/openrig-core/skills/delegating-work/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/mvschwarz/openrig.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.