handoff

Capture development session state into a structured handoff note.

14|6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/tyevans/tackline --skill handoff-tyevans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/handoff
Command: npx skills add https://github.com/tyevans/tackline --skill handoff-tyevans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill captures the essential context and state of a development session, ensuring that work can be seamlessly resumed later, preventing knowledge loss and context switching overhead.

Core Features & Use Cases

  • State Capture: Gathers task status, git working tree state, and key decisions made.
  • Risk Identification: Flags unfinished work, known risks, and open questions.
  • Structured Handoff Note: Generates a clear, actionable document for the next session.
  • Use Case: At the end of a long day of debugging a complex issue, run /handoff to document exactly where you left off, what decisions were made, and what needs to be done next, so you or a colleague can pick it up efficiently tomorrow.

Quick Start

Use the handoff skill to capture the current session's state for a smooth transition.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I capture development session context for a smooth handoff?

To capture development session context for a handoff, this Skill gathers task status, git logs, decisions, discovered patterns, unfinished work, risks, and open questions into a structured transition note. This document provides clear pickup points for future work.

What is the best way to document unfinished work and risks before ending a coding session?

The best way to document unfinished work and risks is using a structured handoff note that flags known risks and open questions alongside current task status. This ensures seamless session resumption by providing clear pickup points and context for future work.

How does session transition documentation help with developer workflow knowledge preservation?

Session transition documentation preserves developer workflow knowledge by capturing key decisions and discovered patterns during a coding session. This prevents knowledge loss and context switching overhead, allowing you or a colleague to efficiently resume work later.

Can I use this handoff note to help a colleague resume my debugging task?

Yes, you can use the generated handoff note to help a colleague resume your debugging task. It documents exactly where you left off, what decisions were made, and what needs to be done next, providing the context needed for efficient pickup.

Do I need any specific dependencies to document my git working tree state?

No specific dependencies are required to document your git working tree state. The Skill operates independently to gather your task status and git logs, creating an actionable handoff document without needing external plugins.

What should I do if my session transition notes are missing key decisions and discovered patterns?

If your session transition notes are missing key decisions and discovered patterns, running a structured handoff capture ensures these elements are automatically gathered. It records task status, risks, and open questions to create an actionable resumption document.