successorlisted

# Successor sessions ## Overview A successor is a **separate OS-level Claude session** — its own context window, its own harness, its own lifetime — launched by `.claude/scripts/odin-relay.sh` and reachable through `claude agents`. Not a subagent. A subagent shares the parent's lifetime, returns text, and dies with the turn; a successor outlives the session that spawned it, pushes commits, and is integrated by branch. **Core principle: a successor knows only what its handoff says.** Everything else it must rediscover at its own cost, or guess at yours. The handoff bar below is therefore the whole skill; the rest is procedure around it. Rigid skill. The phases run in order; the bar has no optional elements. ## When to use | Situation | Fire | |---|---| | Hand THIS session's work forward, one successor | `handoff` skill, or `/relay` — write, launch, monitor (ADR-0077) | | Two or more independent workers, coordinated | **this skill** | | A campaign with waves, per-worker branches | **this skill** | | Parallel work inside one context window | `dispatching-parallel-agents` (subagents, not sessions) | | A delegated session stalled or wedged | **this skill** → Phase 3 | | A worker's branch is ready to land | **this skill** → Phase 4 | One successor = the `handoff` skill (`/relay` is its command form). A coordinated fleet = this skill. **"The successor manager" is a role, and `successor-manager` is the skill that owns it** (ADR-0105). Its occupant is whoever launched the sess