handoff

Capture session context and decisions into a timestamped handoff file.

Updated Jul 27, 2025
One-click install
npx skills add https://github.com/TheCactusBlue/nixfiles --skill handoff-thecactusblue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/TheCactusBlue/nixfiles/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/TheCactusBlue/nixfiles --skill handoff-thecactusblue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture the current session state, decisions, and blockers to create a portable handoff for future work.

Core Features & Use Cases

  • Session recap: Summarizes accomplishments and decisions from the current session.
  • Handoff file creation: Writes a timestamped .claude/handoff file capturing context for the next session.
  • Commitment & traceability: Automatically commits the handoff with a standardized message to preserve history for teammates.

Quick Start

End your session and run the handoff process to generate the timestamped file in .claude/handoff/YYYYMMDD-HHMMSS.md and commit with the message chore: session handoff.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I capture session context for a seamless handoff between work sessions?▼

To capture session context for a handoff, run the handoff process at the end of your work session. It generates a timestamped markdown file in .claude/handoff/ recording accomplishments, notes, and next steps for future reference.

What is the best way to document session decisions and blockers for teammates?▼

Documenting session decisions and blockers is handled by creating a portable handoff file. This file summarizes your current session state and automatically commits to preserve history for teammates.

How do I create a timestamped handoff file for my workflow notes?▼

Creating a timestamped handoff file for workflow notes requires running the handoff process. It writes your session recap to .claude/handoff/YYYYMMDD-HHMMSS.md and commits it with the message chore: session handoff.

Do I need any dependencies to automatically commit session documentation?▼

No dependencies are required to automatically commit session documentation. The handoff process operates independently to generate the timestamped handoff file and commit it directly to your repository history.

Can I use this session-capture process to generate a recap of my accomplishments?▼

Yes, you can use this session-capture process to generate a recap. When applied at the end of a work session, it summarizes your accomplishments and decisions into a portable markdown format.

What limitations should I expect when preserving session history through handoff notes?▼

A limitation of preserving session history through handoff notes is that it requires manual application at the end of each work session to generate the timestamped file, rather than running as a continuous background capture.