giladbarnea/soft-skills / plugins/soft-skills/skills/ai-to-delegated
ai-to-delegated
VerifiedBest practices for getting a step-function leap in productivity when working with other AI’s. Load `ai-to-delegated` before spawning a sub-agent, creating a team, talking to a teammate agent, or writing a doc likely read by other agents. Trigger words include “dispatch an agent”, “spawn a team”, and “fork the session to ...”.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.9 KB |
| briefing/examples.md | markdown | 12.7 KB |
| briefing/forked-context.md | markdown | 613 B |
| briefing/fresh-context.md | markdown | 1.6 KB |
| configurations/colloquium.md | markdown | 2.2 KB |
| configurations/external-advisor.md | markdown | 1.1 KB |
| configurations/hillclimber-watcher/protocol.md | markdown | 4.0 KB |
| configurations/hillclimber-watcher/watcher.md | markdown | 1.5 KB |
| configurations/pair-programming.md | markdown | 5.1 KB |
| configurations/research-fanout.md | markdown | 2.8 KB |
| coordination/budget-balancing.md | markdown | 1.0 KB |
| coordination/delegates.md | markdown | 4.9 KB |
| coordination/leading-leaders.md | markdown | 4.2 KB |
| coordination/many-hours-supervision.md | markdown | 3.6 KB |
| coordination/peers.md | markdown | 2.4 KB |
| planning/choose-configuration.md | markdown | 7.9 KB |
| planning/dispatch-outside-the-harness.md | markdown | 1.3 KB |
| planning/when-to-delegate.md | markdown | 8.7 KB |
coordination/leading-leaders.md
View on GitHub---
name: leading-leaders
description: Fleet-scale delegation — the human leader is the admiral, you are the captain of first mates who lead their own crews. One level above the base leader conduct.
last_updated: 2026-09-19
---
# Captain
The human leader is the admiral. You are the captain.
Before commissioning or supervising leaders, read [delegate coordination](coordination/delegates.md) if it is not already in context. This is the same leader relationship, lifted one level. The admiral sets the mission and makes the decisions that need human judgment. The captain turns the mission into a fleet and keeps the fleet coherent. A ship is one team with one first mate at its head. The fleet is your ships together.
## Chain of command
Admiral → captain → first mates → their crews.
You speak only to first mates. Do not dispatch, steer, or query a first mate's crew directly — that undermines the first mate and creates two sources of truth on one ship. If a ship drifts, steer its first mate. Cross-ship dependencies are yours to sequence; ships do not coordinate with each other except through you.
You do not row, and you do not do a first mate's job either. The delegation parameters in [choose-configuration.md](planning/choose-configuration.md) — shape, concurrency, context, model, thinking — are each first mate's to suggest for its own ship. In a fleet, you occupy the leader seat: their suggestions come to you for approval, their escalations come to you, and you answer without waking the admiral unless the answer needs human judgment.
What is yours to decide: how the mission decomposes into ships, what each ship's mission is, and what each first mate needs to know.
For these decisions, favor the simplest effective approach. As the work progresses, keep clear what matters to the mission and what does not. Do not spend attention on details that look important but do not affect the outcome.
By default, each ship works on an independent git worktree. Confirm this with the admiral.
## Fleet plan
You may suggest a fleet plan — how many ships, each ship's mission, what each brings back — but the admiral must approve it before you commission anyone.
The admiral sets fleet-wide policy in one line ("all first mates on model X at thinking Y, everything below them at thinking Z"). That policy, and every shape you approve for a first mate, is a contract. Enforce it down the chain: an extra delegate nobody approved, or a wrong model or thinking level, is a violation to catch and correct — without waking the admiral.
## Commissioning a first mate
1. Tell it to load [`roles.md`](soft-skills/roles.md) and the skills it routes to; inform it about the chain-of-command, and that you are its captain — its leader: direction, approvals, and escalations flow between it and you.
2. Give it the fleet's why, the slice that is its ship's mission, and the bottom-line added value the fleet needs back from it. Do not prescribe the how — when a first mate lacks your context, read [fresh-context briefing](briefing/fresh-context.md). Its over-fitting warnings apply equally all the way down.
## How a captain communicates with the admiral
Read [`ai-to-leader`](ai-to-leader/SKILL.md) for cold entries and provenance. The escalation bar and batched approvals are in [delegate coordination](coordination/delegates.md). The admiral is your leader; nothing here is fleet-specific.
## Mid-flight steering
Terse steering is normal admiral behavior — "pass that down", a bare link, "yes good". Amplify it downward faithfully, without distortion, and confirm in one line.
## Keep the fleet afloat
Your own context window is important. Each first mate keeps its own ship afloat, and you hold the same duty one level up. [Context window](soft-skills/context-window.md) covers both.
**Easy ways to squeeze more out of your context window:**
- Do not send mini-summarizations after every team exchange. If no action is required from the captain, just respond with a single short sentence (~5–15 words.)
- Use fluffless language when sending messages to teammates. Be clear but do no padding.
**When writing a handoff doc:**
Any memory you persist should cover only your unique scope: the in-between of ships and the link to the admiral. Reference other docs; do not repeat their contents.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |