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/peers.md
View on GitHub---
name: peers
description: How to work alongside teammates — the sideways flavor of leader conduct, minus steering rights.
---
# Peers
Read this when you work alongside teammates. For reports or escalations to your leader, read [ai-to-leader](ai-to-leader/SKILL.md).
If a message requires restoring shared context, read [theory-of-mind](theory-of-mind/SKILL.md).
If you request work from a peer without shared context, read [fresh-context briefing](briefing/fresh-context.md).
Peer conduct applies scope ownership between equals:
- A peer's scope is not yours, same as a delegate's. Trust them to do their work. Do not disrupt it, redo it, or take it over.
- Unlike with delegates, you have no steering rights over peers. Share findings and concerns; never instruct.
- Do share: findings that update the shared terrain, blockers a peer might unblock, and material challenges slowing you down. Live cross-pollination is the point of a team over parallel subagents.
- Keep your status current (see the status guidance below), and read your peers' statuses before pinging them.
## Statuses and early escalation (teams)
**Set your own status frequently.**
- Status format (not strict): `<what happened last>; <what you intend to do>; <whom you’ll message when done>/<whom you’ll await to message you>`. Keep it short.
- Set status that you’re responding before you send a message; set status when you’ve messaged your teammate and are waiting for reply; set status when you’re exploring, implementing, testing, reviewing, blocked, or waiting.
- Fittingly, set status when you have _completed_ the above examples or have received what you have requested.
- Keep statuses short but current so your teammates and main are informed about the true current state.
**Simplistic good status update examples:** (generalize — this is not a comprehensive list):
`Finished exploring, awaiting explorer-2’s ping to brainstorm together`; `Hit a snag trying to achieve X, messaged everyone to help unblock me, awaiting responses`; `Got steer from main, modifying tests accordingly; will ping main when done`; `Ack implementer done writing the code, starting review; will ping implementer when done`.
Another good practice is to low-key live share non-blocking but material challenges slowing you down. Examples: `Mapping the user funnel in the database; FYI, working with a remote database introduces failures and latency.`.
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 |