successor-managerlisted

# successor-manager — ownership, and the verdict ## What this is not for This skill owns two things nothing else owns: **who is responsible for a delegated session**, and **how that session's state is decided from evidence rather than from its own report of itself.** Delegation itself already has an owner. Route there instead. | The task | Its owner | Why not this skill | |---|---|---| | Provisioning, launching, integrating, tearing down; the six-element handoff bar | `successor` | It owns the five phases. This skill starts once a session exists and asks what is true of it. Its bar is cited here, never restated — two copies of a bar drift, and the looser copy wins silently. | | Handing **this** session forward, once | `/relay` | One-off delegation with its own gates. One successor is `/relay`; a fleet is `successor`; this skill is what you consult about either afterwards. | | Planning a multi-successor campaign, waves, campaign closure | `campaign` — harness:RM-0302, **not yet built** | Waves are a different item. The seam is named, not filled: this skill classifies the sessions a campaign launched; it does not decide what a campaign contains or when it is finished. | | Parallel work inside one context window | `dispatching-parallel-agents` | Subagents. They share the parent's lifetime, return text, and die with the turn — there is no register row and no verdict to compute. | | What a session *says* to another session, and what a delegated session's terminal should carry |