compact-handofflisted

# Compact Handoff ## Activation - Produce a handoff only when the user explicitly asks to transfer this work to another session or another agent. The request must be the user's own; a request to shorten, summarize, wrap up, or reduce context is not one. - Never produce a handoff on your own initiative. Low remaining context, a finished task, a long conversation, an approaching session end, or a compaction warning are not requests and must not trigger this skill. - When this skill activates without such a request, emit no handoff. State in one sentence that no handoff was requested and continue with the actual task. ## Output Contract - Output exactly one fenced code block labeled `markdown`. Fence it with four backticks, or with more backticks than any backtick run inside the prompt, so embedded code blocks cannot terminate it. - Put the complete handoff prompt inside that code block. - Always emit Receiver Instructions, Objective, Continuation Anchor, Work State, and Resume Steps. Emit any other section or subsection only when it has content, and omit its heading entirely when it does not. - Output no introduction, explanation, conclusion, or other text outside the code block, except output the user explicitly requested in addition to the handoff. - Use Markdown headings, bullets, numbered steps, and compact key-value entries inside the prompt. Do not use prose paragraphs. - Write all headings, summaries, instructions, and next steps in English, even when t