handoff

Generate HANDOFF.md with git state and project session details.

Updated Sep 9, 2024
One-click install
npx skills add https://github.com/axel-kaliff/dotfiles --skill handoff-axel-kaliff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/handoff
Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill handoff-axel-kaliff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a structured HANDOFF.md to capture the current session state so a fresh agent can continue work without re-deriving context.

Core Features & Use Cases

  • Automatically gathers session state (current branch, git status, recent commits, stash list) and records it in HANDOFF.md.
  • Enforces a standardized HANDOFF.md structure with sections for Branch, Goal, What Was Done, User Decisions, In Progress, Known Issues, Unstaged / Uncommitted Changes, Next Steps, and Key Files.
  • Intended for handoffs when a session should stop or context is too high, ensuring continuity across agents.

Quick Start

Run the handoff workflow to generate HANDOFF.md at the project root and stop.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a handoff document for an AI agent to continue my session?

To create a handoff document, you generate a HANDOFF.md file at the project root that captures the current git branch, status, recent commits, and stash list so a new agent can pick up where you left off.

What should a session handoff document include for software projects?

A session handoff document should include sections for the current branch, project goal, what was done, user decisions, in-progress work, known issues, unstaged changes, next steps, and key files.

When do I need to generate a handoff document for my project?

You need to generate a handoff document when your current AI session is stopping due to high context limits or when you explicitly request a workflow handoff to ensure continuity across agents.

How do I capture git state for an AI agent handoff?

Capturing git state for an AI agent handoff involves automatically gathering the current branch, git status, recent commits, and stash list, then recording this information directly into the HANDOFF.md file.

Can I use a structured handoff workflow to manage context limits across agents?

Yes, you can use a handoff workflow to manage context limits by stopping the current session and generating a standardized HANDOFF.md file that provides a fresh agent with the full project state.

What is the best way to transfer session state between AI agents?

The best way to transfer session state is to create a structured HANDOFF.md file at the project root that records the git state and required context sections, ensuring a new agent can continue work immediately.