Hand-Off Session

Response Format

Begin the first response to this skill invocation with the line:

Entire Session Handoff:

followed by a blank line, then the content. The header applies to the full compaction-summary flow, including the "Unanswered Question" branch (which is still a successful run — the skill summarized the transcript and surfaced the question).

• Apply the header to the first response of the invocation only. Do not re-print it on follow-up turns within the same invocation (e.g. after the user answers the surfaced unanswered question).
• Do not include the header on error or early-exit responses (e.g. no .git/entire-sessions/ directory, no sessions found after filtering, transcript file missing at the path the session JSON points to). The header's presence should signal that the skill ran and produced real output.

STOP — Read these rules before doing ANYTHING

1. Do NOT ask clarifying questions. Auto-detect the session and read the transcript.
2. Do NOT run entire sessions list, entire sessions info, entire explain --session, git log, git status, git branch, ps aux, or any other exploratory commands. They waste time and don't give you the transcript.
3. Do NOT say "Would you like me to continue?" or "Let me know if you want me to pick this up." Just read the transcript and start working. (Exception: if the previous agent asked the user a question that was never answered, you MUST ask the user that question before proceeding.)
4. Do NOT summarize the session as having "0 turns" or "no progress" without first reading the actual transcript file. The entire CLI metadata often undercounts — the transcript is the source of truth.