Handoff
Purpose
Write a concise handoff document so a fresh agent or later session can continue from verified facts instead of replaying chat history.
Save the document to the operating system temp directory, not the current workspace:
- Windows:
$env:TEMP
- macOS/Linux:
$TMPDIR when set, otherwise /tmp
Use a filename like agent-handoff-YYYYMMDD-HHmm-<slug>.md.
Workflow
- Identify the next-session focus from the user's request. If they gave arguments, treat them as the handoff focus.
- Inspect current repo state only when it affects the handoff: branch, changed files, relevant artifacts, and recent validation results.
- Write the temp Markdown document.
- Link the created file in the response and summarize the restart path in one or two sentences.
Document Contract
Include only sections that add useful restart context:
- Goal and current status.
- Verified facts and evidence paths.
- Decisions already made.
- Files changed or likely relevant.
- Commands run and results.
- Open questions, risks, and blockers.
- Suggested skills for the next agent.
- Next concrete actions.
Reference existing PRDs, plans, ADRs, issues, commits, diffs, reports, or HTML artifacts by path or URL instead of duplicating them.
Safety
- Redact secrets, credentials, tokens, passwords, and personally identifiable information.
- Do not include hidden reasoning or private chain-of-thought.
- Label assumptions as assumptions.
- Do not write to the repo unless the user explicitly asks for a durable repository handoff.
- Do not commit, push, publish, or mutate remote state while creating the handoff.
Use effective-interact instead when the user asks for a visual final report, material repo-change handoff, review artifact, or HTML artifact. Context compaction remains a native Host/main-Agent decision; this Skill only writes restart notes.
1---2name: handoff3description: Load when a task needs to hand off current work, compact a conversation for another agent/session, or create restart notes; do not load for visual HTML repo reports.4license: MIT5---67# Handoff89## Purpose1011Write a concise handoff document so a fresh agent or later session can continue from verified facts instead of replaying chat history.1213Save the document to the operating system temp directory, not the current workspace:1415- Windows: `$env:TEMP`16- macOS/Linux: `$TMPDIR` when set, otherwise `/tmp`1718Use a filename like `agent-handoff-YYYYMMDD-HHmm-<slug>.md`.1920## Workflow21221. Identify the next-session focus from the user's request. If they gave arguments, treat them as the handoff focus.232. Inspect current repo state only when it affects the handoff: branch, changed files, relevant artifacts, and recent validation results.243. Write the temp Markdown document.254. Link the created file in the response and summarize the restart path in one or two sentences.2627## Document Contract2829Include only sections that add useful restart context:3031- Goal and current status.32- Verified facts and evidence paths.33- Decisions already made.34- Files changed or likely relevant.35- Commands run and results.36- Open questions, risks, and blockers.37- Suggested skills for the next agent.38- Next concrete actions.3940Reference existing PRDs, plans, ADRs, issues, commits, diffs, reports, or HTML artifacts by path or URL instead of duplicating them.4142## Safety4344- Redact secrets, credentials, tokens, passwords, and personally identifiable information.45- Do not include hidden reasoning or private chain-of-thought.46- Label assumptions as assumptions.47- Do not write to the repo unless the user explicitly asks for a durable repository handoff.48- Do not commit, push, publish, or mutate remote state while creating the handoff.4950Use `effective-interact` instead when the user asks for a visual final report, material repo-change handoff, review artifact, or HTML artifact. Context compaction remains a native Host/main-Agent decision; this Skill only writes restart notes.
JasonxzWen