handoff-orchestrator
Skill5 starsChanged 54 days agoMITView on GitHub
Use when an approved work scope moves to a new orchestrator in its own Herdr tab.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-feedbackSkill
- asking-peer-agentsSkill
- boss-assistantSkill
- boss-saySkill
- bringing-coworkerSkill
- choosing-graphSkill
- contacting-orchestratorsSkill
- create-great-harnessSkill
- dispatching-workSkill
- i-am-orchestratorSkill
- initSkill
- notifying-main-agentSkill
- peeking-workSkill
- reporting-to-userSkill
- resolving-appSkill
- shipping-taskSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Run handoff-orchestrator.py with --user-approved, this pane, cwd, provider, and the continuity fields.
- Distinctive: line 31
When none is retained, let the launcher close this pane after it emits the accepted result.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hand off one orchestrator scope
1. Get approval
A handoff creates another user-facing window, so the current main agent first presents one approval decision, naming the scope that moves and any work this orchestrator retains. A new tab is created only after the user approves.
2. Carry continuity
Pass only goal and scope, confirmed decisions and user terms, current state and evidence, next action, and exclusions. Omit empty fields and conversation text.
3. Launch and transfer
Run handoff-orchestrator.py with --user-approved, this pane, cwd, provider, and the continuity fields.
Pass --dispatch for each in-progress dispatch in the moving scope; a handoff that retains nothing lists every dispatch this pane coordinates.
The script creates and labels an independent tab, starts the receiving orchestrator, prompts it to invoke boss-say and then accept, and verifies the handshake after that route is established.
It waits up to two 120-second acceptance windows, re-offering only to a receiver that stopped without accepting, so give the command a tool timeout of at least five minutes.
Final failure closes the new tab and leaves ownership here.
4. Leave the scope
On acceptance, status events, investigation, scheduling, reporting, and cleanup all belong to the receiver.
Report the new tab and transferred scope compactly.
Continue only the scope passed through --retains.
When none is retained, let the launcher close this pane after it emits the accepted result.
Complete when: the receiver accepted and this orchestrator left the scope, or the failed new tab is closed and ownership remains here.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.