skills.rest
asarchami
asarchamiCOMMUNITY
Explore all skills by this author →
GitHub

handoff

Writes a compact handoff document summarizing session state for the next agent.

1|2|Updated Nov 25, 2017
Search Tags:#documentation#agent workflow#knowledge transfer#handoff#session summary#context compaction
One-click install
npx skills add https://github.com/asarchami/dotfiles --skill handoff-asarchami
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/asarchami/dotfiles/tree/main/dot_config/opencode/skills/handoff
Command: npx skills add https://github.com/asarchami/dotfiles --skill handoff-asarchami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a working session ends, the next agent or teammate normally has to re-read the entire conversation to continue. This Skill compacts the session into a short handoff document so work resumes without losing context. ## Core Features & Use Cases - Session Compaction: Summarizes current state, key decisions, next actions, and open questions into a one-screen document. - Artifact Referencing: Points to specs, PRDs, ADRs, issues, commits, and diffs by path or URL instead of duplicating their content. - Safety and Hygiene: Redacts secrets and PII, verifies suggested skills exist, and saves the file to the OS temp directory rather than the workspace. - Use Case: After a long debugging or design session, invoke the handoff skill to produce a dated markdown file the next agent reads in minutes to pick up exactly where you stopped. ## Quick Start Use the handoff skill to write a handoff document for this session so a fresh agent can continue the work tomorrow.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off an AI agent session to a new agent?▼

Invoke the handoff skill at the end of the session. It assembles the current state, decisions, next actions, and artifact references into a compact markdown document that the next agent reads to resume work without the original conversation.

What should a session handoff document contain?▼

A handoff document contains current state, decisions with rationale, ordered next actions, open questions, suggested skills for the next agent, and paths or URLs to artifacts like specs, PRDs, ADRs, issues, commits, and diffs.

Where is the handoff document saved?▼

The document is saved to the OS temp directory ($TMPDIR on Unix/macOS, %TEMP% on Windows) as <project>-handoff-<YYYY-MM-DD>.md. It is deliberately kept out of the workspace because it is transient.

Does the handoff skill remove secrets from the document?▼

Yes. Before saving, the skill scans the draft for API keys, passwords, tokens, and personally identifiable information and redacts them so no sensitive value survives in the final document.

When should I not use a handoff document?▼

Avoid it when the work is fully captured in durable artifacts like committed code or updated specs, since the handoff must never duplicate artifact content. It is meant for transient session context, not permanent documentation.

Related Skills

Explore More Software Engineering Skills→
hbvg234hbvg234
1

handoff

Summarize the current conversation into a structured handoff document referencing artifacts by path or URL.

Community
Intermediate
fercosntfercosnt

handoff

Generates a handoff document summarizing the current conversation for a fresh agent session.

Community
Basic
Dev10x-GuruDev10x-Guru
7

Dev10x:gh-pr-create

Automate GitHub pull request creation with ticket extraction and Job Story summaries.

Official
Advanced
plurigridplurigrid
60

chromatic-walk

Coordinate three-agent codebase exploration using GF(3)-balanced prime geodesics.

Official
Advanced