handoff

Enumerate session tasks and save timestamped handoff documents to .agent-memory/handoff/.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill handoff-hve4638
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/common/skills/handoff
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill handoff-hve4638

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams wrap up a Claude session by capturing and organizing context into future-ready handoff documents for the next Claude session.

Core Features & Use Cases

  • Enumerates all session tasks and context to avoid loss.
  • Clusters tasks by cohesion, suggests groupings, and auto-generates memory documents under .agent-memory/handoff/.
  • Auto-saves timestamped folders with stable INDEX.md and 2-digit numbered task files for clean handoff continuity.

Quick Start

Initiate the handoff to create timestamped task documents under .agent-memory/handoff/ and save them without overwriting prior files.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer session context to a new Claude instance?▼

To transfer session context, the Skill enumerates all tasks performed, proposes cohesive groupings, and auto-saves timestamped memory documents under .agent-memory/handoff/ for the next Claude to read.

What is the best way to document Claude session tasks for knowledge transfer?▼

The best way to document tasks for knowledge transfer is clustering them by cohesion, confirming the groupings, and auto-generating structured memory documents using an INDEX.md plus NN-<slug>.md scheme.

Does the handoff process overwrite previous session memory files?▼

No, the handoff process enforces non-overwriting storage by creating timestamped folders under .agent-memory/handoff/, ensuring prior session context and task documents remain intact.

Can I automate task documentation without losing prior session history?▼

Yes, you can automate task documentation by initiating the handoff workflow, which captures current session context and saves it alongside prior history without overwriting existing memory files.