handover

Files (1)

• SKILL.md

SKILL.md (first lines)

# handover

```bash
${CLAUDE_PLUGIN_ROOT}/scripts/orchestrate.sh handover <programme> "<reason>"
```

Writes `HANDOVER.md` in the programme dir, records a `handover` event with the
reason, and releases the lock last.

The ownership token is spent by this. The programme is left deliberately
unclaimed, and the next orchestrator claims a fresh token through
`orchestrate:takeover`, which is recorded. A tick will not quietly pick a
handed-over programme back up.

## The brief is generated, never authored

It is built from `lanes.jsonl`, `events.jsonl`, `hosts.jsonl` and `reviews/`:
lanes and their states, PR ownership, owed notices, reviews on disk, the last
twenty decisions and steers, host pressure, and one next action. A brief written
by hand goes stale the moment the next tick runs; this one cannot.

Do not add prose to it. Anything the next orchestrator must know permanently
belongs in `ORCHESTRATION.md`, which every tick reads. Anything about one
decision belongs in a `decision` event, so a later tick can see what was told to
whom.

## Before handing over

1. Run one tick, so the index reflects reality rather than a stale reading.
2. Drive `owed` to zero. A lane left awaiting a verdict on a merged PR is the
   single most expensive thing to hand over.
3. Then run handover, and tell whoever is next the one line they need:
   `orchestrate:takeover <programme>`.

## Credit guard: yours, not the script's

No code reads `handover.credit_threshold_pct`. Nothing checks your usage, and
no tick will run handover for you. If your harness does not expose the
orchestrator's own usage number, that key does nothing at all.

Where the harness does expose it: watch it yourself, and run this verb before
you run out rather than after. A session that runs out mid-loop is recovered by
`orchestrate:takeover`, not prevented.

## The programme dir is host-local

Taking over on a different machine needs that directory copied there first, or
the same machine used. Say which you did.

From stevengonsalvez/ainb-toolkit, MIT.

More from stevengonsalvez/ainb-toolkit