coordinating-peer-sessionslisted

Rules for working alongside other Claude Code sessions the user started in parallel. Defines the four coordination channels (Linear and Git, the ledger, `ListAgents`, `SendMessage`), the seven message occasions (LANDED, CLAIM, CONFLICT, SOLVED, READY, ASK, ORIGIN), and the permission boundary a peer message can never cross. Carries change provenance: how to tell what this session wrote from what it found, via `change-provenance.sh`, and how to get the intent behind a foreign change from the session that wrote it. Activates on "peer session", "andere Session", "wer arbeitet gerade woran", "wer hat das geändert", "fremde Änderungen", when `ListAgents` shows live peers, when a message arrives, when a review or ship meets uncommitted work nobody in this session made, or when a change affects a repo a peer consumes. NOT for agent teams this session spawns (use coordinating-agent-teams). NOT for subagents (use the Agent tool directly).
lenneTech/claude-code · ★ 0 · Code & Development · score 72

Install: claude install-skill lenneTech/claude-code

# Coordinating Peer Sessions The user runs several Claude Code sessions at once: one `/lt-dev:ticket-cycle` per ticket, a base-repo session next to a customer-project session, a long test run beside active development. Those sessions are **peers**. Nobody spawned them, nobody leads them, and each one steers its own work. A session can list its peers (`ListAgents`) and send a peer one plain-text message (`SendMessage`). This skill is about using that sparingly and correctly, because a delivered message costs the receiving session a full prompt and lands in the middle of its work. ## The four channels, in this order Reach for the cheapest channel that carries the information. Messaging is the last one, not the first. | Channel | Cost | Carries | Survives session end | |---|---|---|---| | **1. Linear and Git** | free | Which ticket is claimed, which branch exists, what is pushed, what is merged | yes | | **2. The ledger** (`peer-ledger.sh`) | free, disturbs nobody | Open claims on cross-cutting work, and diagnoses worth keeping | yes | | **3. `ListAgents`** | free, disturbs nobody | This session's own name, and which sessions are alive right now | no | | **4. `SendMessage`** | one prompt at the receiver, interrupts its rhythm | Intent, uncommitted state, and anything that has to reach a peer *now* | no | The first two answer questions without anyone noticing, and their answers are still there tomorrow. Reading them before sending anything is what keeps the message count lo