zwrose

showrunner-handoff

"Use in the showrunner advisor seat you are leaving while it is still alive — deliberate handover before the seat goes dark. Leaves durable state for the incoming seat. Emits no paste block. Not checkpoint (`/compact`); not showrunner-resume (incoming seat)."

zwrose 1 Updated 1mo ago
GitHub

Install

npx skillscat add zwrose/superheroes/showrunner-handoff

Install via the SkillsCat registry.

SKILL.md

This skill speaks in host-neutral actions. Resolve them to your runtime's tools by reading the host tool map at ${CLAUDE_PLUGIN_ROOT}/hosts/<your-host>-tools.md (the leading variable is this plugin's root directory) — claude-tools.md on Claude Code, codex-tools.md on Codex.

showrunner-handoff — hand the advisor seat over

Run this in the showrunner advisor seat you are leaving, while that seat is still alive and you have time to hand over deliberately. It prepares durable state for the incoming seat and closes with the verdict Step 5 defines. It does not emit a block of text for the owner to paste — nothing is handed over by text, so nothing can go stale.

Refuse plainly and stop when this is not a showrunner advisor session. Emit no partial output.

Invocation

Form Behavior
/superheroes:showrunner-handoff Ask whether this instance's account is going dark, prepare durable state, stop this seat's background tasks, freshen the resume point if one exists, and close (Step 5). Refuse plainly when this is not a showrunner advisor session.

Step 1 — the one question

Ask the owner exactly one question: is this instance's account going dark?

Ask nothing else. This is the only fact that changes what happens to the builders — whether they must park and push before the account stops, or keep running untouched.

Step 2 — the park-and-wait branch

If yes: ask every live builder launched from this account to park and push — enumerate them from the launch ledger's live launches and the leader process each lane's own launch record names, never a global process match. The request travels through whatever channel this host offers for reaching another session. Where the host offers none, the request cannot be delivered — name those lanes and carry them to step 5 as unresolved rather than implying a park was asked for.

Then wait on durable evidence only, never on a message being acknowledged:

  • a park record on the lane's issue or pull request;
  • the lane's builder-liveness heartbeat reaching a terminal state;
  • the launch ledger carrying that lane's terminal outcome.

The wait is a bounded poll over those artifacts. A lane that does not resolve inside the bound is carried to step 5 by name — it is never waited on forever and never assumed parked.

If no: the builders keep running, untouched. Say so explicitly. Step 5 will state it, so the new seat is not left guessing whether lanes were stopped.

Step 3 — stop this seat's background tasks

Use the host-neutral action to stop every background task this session started — watch loops and any other wait or poll — and name each in step 5. The work a stopped task was waiting on passes to the incoming seat through the resume point. Never kill a builder's leftover child process: it can block record-outcome and is not this seat's.

When a task cannot be confirmed stopped, name it in step 5 as unresolved. Do not assume it stopped.

Step 4 — freshen the resume point

When this session keeps a resume point, freshen it; when it does not, say so and continue — invent no format, path, or filename. The shape and lookup are the same ones skills/checkpoint/SKILL.md under this plugin's root defines.

Whether the write succeeded, failed, or there was nothing to write is carried to Step 5.

Step 5 — close

The closing output is one short block. Which shape it takes is decided here, once:

  • Ready. is legal only when nothing is unresolved (every live lane of this account reached durable park or terminal evidence when the park branch ran; every watch loop this seat armed was confirmed stopped) and the resume point was freshened by a write that succeeded.
  • Otherwise the close is Not ready — <n> unresolved. naming each item and what failed — a builder that could not be reached, park evidence that could not be read, a loop not confirmed stopped, a resume-point write that failed, or no resume point kept by this session to freshen (Step 4 invents none, so there was no successful write). Say plainly that the incoming seat will find these as they stand and resolve them from durable state, and that the handoff does not wait on them.

Worked example (not ready — one unresolved lane)

Not ready — 1 unresolved. Account going dark — lanes #412 and #415 parked: park records on their issues, heartbeats terminal, ledger outcomes recorded. Lane #418 unresolved: no host channel to reach its builder; park not requested. Watch loops for batch wave-handoff-a stopped. The incoming seat will find lane #418 as it stands and resolve it from durable state; this handoff does not wait on it.

Worked example (not ready — resume-point write failed)

Not ready — 1 unresolved. Account not going dark — builders keep running. Watch loops for batch wave-handoff-b stopped. Resume-point write failed: ledger top pointer could not be updated. The incoming seat will find this as it stands and resolve it from durable state; this handoff does not wait on it.

Worked example (ready — all lanes resolved)

Ready. Account going dark — lanes #412 and #415 parked: park records on their issues, heartbeats terminal, ledger outcomes recorded. Watch loops for batch wave-handoff-a stopped. Resume point freshened by successful write.

No paste block

This skill emits no block of text for the owner to paste. A block of text is stale the moment the durable record moves past it, and the incoming seat reads the durable record anyway.

Failure modes

Failure Outcome
This is not a showrunner advisor session Refuse plainly. Stop. No partial output.
The ledger or resume point cannot be read Preserve the fact as unresolved. Name it in step 5.
A builder cannot be reached Preserve the lane as unresolved. Name it in step 5.
Park evidence cannot be read Preserve the lane as unresolved. Name it in step 5.
A watch loop cannot be confirmed stopped Preserve the batch as unresolved. Name it in step 5.
The resume-point write fails Name it in Step 5.

Common mistakes

Mistake Fix
Running this in a workhorse or detective session Refuse plainly — this skill is for the showrunner advisor seat only.
Emitting a paste block for the incoming seat The incoming seat reads durable state; nothing travels by text.
Waiting on a builder's acknowledgment Wait only on durable evidence: park record, terminal heartbeat, ledger outcome.
Assuming a lane parked when evidence is missing Name it unresolved in step 5; never assume.
Inventing a resume-point path or format Only freshen a resume point this session already keeps; cite checkpoint for the shape.
Killing watch loops or matching processes to stop them Stop only background tasks this session armed; a process listing is a read, never a kill.