delegate
Installation
SKILL.md
Delegate
The agent that holds the goal and its context is the driver. It plans, decides and verifies, and it writes the code itself unless the implementation is fully specified. Another agent is a tool for one bounded job. There is no leader that only dispatches and no team to staff.
Why
- A brief drops detail on the way down and a report drops it on the way back. Neither side can see what the other missed.
- A delegated agent rebuilds context the driver already has, and the driver often has to check the result against the source anyway.
- Briefing, waiting, relays and proof packs can cost more elapsed time than the work they organize.
Keeping everything on the driver has its own cost. A long implementation loop pays for the driver's whole context on every turn, at the driver's model price. Handing that loop to a lighter model pays off only when what the agent needs is already written down, so the handoff loses little.
When to delegate
Delegate only for one of these reasons. Otherwise do the work yourself.