| name | delegation-playbook |
| description | Delegation protocol, loop prevention, parallel vs sequential execution, result/failure handling, team management, and instance configuration tips for the fleet coordinator |
| roles | ["general"] |
Delegation Protocol
Every delegation via send_to_instance() MUST include:
- Task scope — what exactly to do, bounded clearly
- Expected output — what to return and in what form
- Policy reminder — "Follow Development Workflow policy" (for code tasks)
Loop Prevention
- Never re-delegate a task back to the instance that sent it to you
- If a task has bounced 3 times, stop and solve locally or reduce scope
Execution Strategy
- Parallel — use only when tasks are independent with no shared state
- Sequential — use when one task's output feeds into the next
Result Handling
When an instance reports back, classify the outcome:
- Success → Summarize key results for user. Omit internal coordination noise.
- Partial → State what succeeded, what remains, proposed next steps.
- Failure → Retry up to 2 times. If still failing: try alternative instance, reduce scope, or return partial result clearly marked.
- No response → Ping again after reasonable wait. If still silent: report to user with options.
Shared Decisions
Use post_decision() / list_decisions() for any choice that affects more than 1 instance, changes an API contract, introduces a new dependency, or alters deployment process.
When instances disagree, collect both viewpoints, make a decision, and record it via post_decision.
Team Management
- Always check existing teams before creating new ones
- Default to ephemeral teams (created for a specific task, dissolved after completion)
- Clean up ephemeral teams and instances after task completion
Instance Configuration Tips
When users create specialized instances, suggest these configurations:
- Reviewer instances: Add
pre_task_command: "/chat load reviewer-base" to reset context before each review, preventing influence from previous conversations.
- Collab mode: For multi-bot channels, use
/collab to enable @mention-based triggering.
- Cost control: Set per-instance
cost_guard for expensive backends.
