handoff

Generate a structured HANDOFF.md from session context and investigation results.

2|1|Updated Feb 8, 2021
One-click install
npx skills add https://github.com/jstoobz/dotfiles --skill handoff-jstoobz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/jstoobz/dotfiles/tree/main/claude/skills/session-kit/handoff
Command: npx skills add https://github.com/jstoobz/dotfiles --skill handoff-jstoobz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a HANDOFF.md to share complete session context and investigation results with teammates who weren't involved. This helps ensure any future reader understands the background, decisions, and next steps without needing to review the entire conversation.

Core Features & Use Cases

  • Structured handoff: Creates a HANDOFF.md with sections for Background, What Was Done, Key Findings, Changes Made, Current State, Recommendations, Risks & Caveats, and References.
  • Versioned handoffs: If an existing HANDOFF.md is present, preserves previous content under a "## Previous Handoff" section and appends the new content as the primary update.
  • Audience-aware: Tailors content for engineers or teammates who were not in the session, avoiding internal prompts or session mechanics details.
  • Linkable references: Captures links to related files, tickets, dashboards, or PRs to enable deeper digging.

Quick Start

Provide the session context and any prior HANDOFF.md; the tool will create or update HANDOFF.md in the current directory, preserving previous versions if one exists.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I generate a HANDOFF.md for team knowledge transfer?

To generate a HANDOFF.md for team knowledge transfer, provide your session context and any prior handoff file. The skill reads the conversation and outputs a structured markdown document with sections for background, key findings, changes, and next steps for teammates.

What is the best way to document session recaps for teammates who were absent?

Documenting session recaps for absent teammates is best handled by creating a structured handoff document. This process captures the problem background, actions taken, and recommendations, ensuring future readers understand the full context without reviewing the entire session.

Can I update an existing handoff document without losing previous context?

Yes, you can update an existing handoff document without losing context. If a HANDOFF.md file is already present, the skill preserves previous content under a "## Previous Handoff" section and appends the new content as the primary update.

How does the generated handoff document handle links to related files and tickets?

The generated handoff document handles links to related files and tickets by capturing them in a dedicated References section. It includes linkable references to related files, tickets, dashboards, or PRs to enable deeper investigation for the engineering team.

Do I need any specific dependencies or components to create a handoff document?

No, you do not need any specific dependencies or components to create a handoff document. The skill operates independently by reading your current conversation or document context and outputting the structured markdown file directly in your current directory.