session-handoff

Generate structured HANDOFF.md documents with session decisions, file paths, and next steps.

2|Updated Jan 3, 2026

Search Tags:#workflow #template #documentation #context #handoff #notes #session

Ready to run

npx skills add https://github.com/jlaws/dotfiles --skill session-handoff-jlaws

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/workflow/session-handoff
Command: npx skills add https://github.com/jlaws/dotfiles --skill session-handoff-jlaws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured HANDOFF.md document that preserves decisions, file paths, test results, and next steps between sessions, ensuring context is not lost when pausing, switching tasks, or ending a session.

Core Features & Use Cases

Generates a standardized HANDOFF.md with sections for Created date, Branch, Status, Summary, Key Decisions, Files Modified, Test Results, Open Issues, Next Steps, and Context.
Supports resuming work after interruptions by providing a clear resume protocol and a sample template.
Suitable for handoffs between teammates, agents, or different sessions to maintain continuity.

Quick Start

Create a HANDOFF.md at the project root and populate it with your current session details using the provided template.

Frequently Asked Questions about session-handoff

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

FAQPage Schema

How do I preserve context and decisions when handing off a coding session to a teammate?▼

Create a structured HANDOFF.md document to preserve decisions, file paths, test results, and next steps between sessions. It enforces a standard template ensuring context is not lost when pausing, switching tasks, or transferring work.

What should a session handoff document include to ensure seamless work continuity?▼

A session handoff document should include sections for Summary, Key Decisions, Files Modified, Test Results, Open Issues, Next Steps, and Context. This standardized structure captures all critical project state needed for seamless continuity.

How do I resume work on a project after an interruption or break?▼

Resume work after interruptions by following a clear resume protocol provided in the HANDOFF.md. The document's structured next steps and context sections allow you or another agent to quickly pick up exactly where the previous session ended.

What's the best way to document project state for multi-session workflows?▼

The best way to document project state for multi-session workflows is generating a standardized HANDOFF.md at the project root. It maintains continuity across different sessions by tracking branch status, open issues, and modified files.

Does the handoff template work for handing off to AI agents as well as human teammates?▼

Yes, the handoff template supports handoffs between teammates, agents, or different sessions. The structured markdown format provides clear context and next steps that both human developers and AI agents can parse to maintain workflow continuity.