| name | po-handover |
| description | Write a PO-session handover file and rotate the session safely — the PO counterpart of disposable worker sessions. Run at 50-60% context usage, or at a natural boundary (a gate just closed, a wave just finished), BEFORE judgment degrades. The new session resumes with /po-resume. Triggers - "po-handover", "prepare the handover", "rotate the PO session". |
po-handover — PO session rotation (sending side)
English | 日本語
Principle: a PO's state belongs in canonical docs, ledgers, and the inbox —
state that exists only in context is itself a defect. The handover file is a
map plus the in-flight deltas that cannot be re-measured — never a memory
dump. Rotate before confusion, not after.
When to rotate
- Context usage reaches 50-60% (confusion past 60% is a measured symptom).
- A natural boundary: a gate closed, a wave completed.
- You notice degraded judgment (late, but better than not rotating).
A refresh is free — same philosophy as workers' "free refresh before a paid
model boost".
Procedure
1. Write the handover file
Fixed path: <po-dir>/handover/<space>.md (your project's PO operations
directory). Template:
# PO handover: <space>
- rotated: <date time> / outgoing session's role: <one line>
## In-flight (ONLY what cannot be re-measured)
Gates awaiting GO:
Expected verdicts/receipts:
Promises to lanes / the owner: <"report when X" items — or "none">
Recent directives not yet in canonical docs:
(or "none", stated explicitly)
:
Operations doc:
Ledgers:
Flow canon:
