po-handoverlisted

# po-handover — PO session rotation (sending side) **English** | [日本語](SKILL.ja.md) **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: ```markdown # PO handover: <space> - rotated: <date time> / outgoing session's role: <one line> ## In-flight (ONLY what cannot be re-measured) - Gates awaiting GO: <which, whose approval — or "none"> - Expected verdicts/receipts: <from whom, landing at which path> - Promises to lanes / the owner: <"report when X" items — or "none"> - Recent directives not yet in canonical docs: <content + source; having any is itself a warning sign> ## Monitor re-arm list (monitors die with the session — mandatory) - <each Monitor's description and full command with all arguments> - (or "none", stated explicitly) ## Inbox baseline - <inbox dir>: <processed up to this file (top of ls