session-handofflisted

# Session Handoff Use this skill when the user asks for a handoff, project handoff, next-Agent summary, continuation notes, `PROJECT_HANDOFF`, `交接文档`, `项目交接`, or similar recovery context. ## Output Policy Default canonical output: ```text <PROJECT_ROOT>/PROJECT_HANDOFF.md ``` `PROJECT_HANDOFF.md` is the single handoff source of truth by default. Include a short English `Agent Brief` at the top for machine/agent scanning, then write the remaining sections in the user's or project's primary language. Optional full translated mirror: ```text <PROJECT_ROOT>/项目交接.md ``` Create or update the optional mirror only when the user explicitly asks for Chinese handoff output as a separate file or a workflow requires a full translated copy. If both files exist and conflict, treat `PROJECT_HANDOFF.md` as authoritative. ## Privacy Rules Never write secrets, tokens, cookies, passwords, credentials, authorization headers, sensitive memory dumps, or raw session logs into handoff files. For public examples, use placeholders such as: ```text <PROJECT_ROOT> <MALTS_ROOT> ``` ## Workflow 1. Inspect the current project state before writing conclusions. 2. Check git status when the workspace is a git repository. 3. Read relevant project instructions, `PROJECT_CONTROL.md`, the active Phase, the active Session if one exists, the current report/handoff, and key files. 4. Distinguish verified current facts from historical claims. 5. For workspace schema v3, run read-only `validate` first. St