handoff

Generates a handoff document and kickoff prompt summarizing a conversation for the next agent session.

Updated May 7, 2026
One-click install
npx skills add https://github.com/jecg2804/HumanOS --skill handoff-jecg2804
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/jecg2804/HumanOS/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/jecg2804/HumanOS --skill handoff-jecg2804

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a working session ends, context is lost and the next agent or session must re-derive decisions, file locations, and pending tasks. This Skill compacts the current conversation into a portable handoff document so a fresh agent can resume work immediately. ## Core Features & Use Cases - Conversation Compaction: Summarizes the current session into a handoff document saved to the OS temporary directory, referencing existing artifacts (PRDs, ADRs, plans, commits) by path instead of duplicating them. - Mandatory Kickoff Prompt: Always produces a copy-pasteable startup prompt containing the handoff path, must-read artifacts, the immediate task, non-skippable gotchas, and suggested skills to invoke. - Safety and Tailoring: Redacts sensitive data such as API keys and personal information, and adapts the document to user-provided arguments describing the next session's focus. - Use Case: After a long debugging session on a Supabase-backed Next.js app, invoke the handoff skill so the next session starts with the exact task, the ADRs to read, and the verification steps that must not be skipped. ## Quick Start Ask the agent to create a handoff for the next session, optionally describing what that session will focus on.

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 conversation?▼

Invoke the handoff skill at the end of your session. It writes a summary document to your OS temporary directory and outputs a copy-pasteable kickoff prompt that points the next session to the document, key artifacts, and the immediate task.

What should a handoff document for an AI coding agent include?▼

A handoff document should include the absolute path to the handoff file, 2-4 must-read artifacts such as ADRs or status docs, the immediate next task, non-skippable gotchas like mandatory verifications, and the skills the next agent should invoke.

Does the handoff skill duplicate existing project documentation?▼

No. The skill explicitly avoids duplicating content already captured in PRDs, plans, ADRs, issues, commits, or diffs. It references those artifacts by path or URL instead of copying their contents.

Can I specify what the next session should focus on?▼

Yes. You can pass an argument describing the next session's purpose, and the skill tailors the handoff document and kickoff prompt accordingly, prioritizing the relevant tasks and context.

Does the handoff document protect sensitive information?▼

Yes. The skill redacts sensitive data such as API keys, passwords, and personally identifiable information before writing the handoff document, so secrets are not carried into the next session.