handoff

Create structured handoff notes and commit them to git.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/hankh95/yurtle-kanban --skill handoff-hankh95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/hankh95/yurtle-kanban/tree/main/skills/handoff
Command: npx skills add https://github.com/hankh95/yurtle-kanban --skill handoff-hankh95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handing off active work between agents with full context is error-prone without a clear process and artifacts.

Core Features & Use Cases

  • Structured Handoff Template: Creates standardized handoff notes with expedition, from/to, created time, status, and context.
  • Context Preservation: Updates the ship's log and ensures current state is captured in git.
  • Use Case: When a task must be handed to agent-d after a switch, the tool generates a handoff note and ship log entry.

Quick Start

Use the handoff skill to prepare a handoff for EXP-123 to agent-b including any notes.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off an ongoing task to another agent with full context?

To hand off ongoing tasks with full context, you generate a standardized handoff note and update the ship log. This template captures expedition, from/to, status, and context, ensuring continuity for the receiving agent.

How does a kanban workflow handle context preservation during agent handoffs?

Context preservation during agent handoffs works by creating a handoffs directory, generating standardized notes, and updating the expedition ship log. This captures the current state and commits changes to git.

Can I use git to track context handoffs for expedition-based workflows?

Yes, you can use git to track context handoffs for expedition-based workflows. The process creates a handoffs directory, updates the expedition ship log, and commits all changes to git for continuity.

What is the best way to maintain work continuity when switching agents mid-task?

The best way to maintain work continuity when switching agents is to enforce a documented handoff note template. This captures expedition, from/to, created time, status, and context before committing changes to git.

Do I need a specific handoffs directory to manage agent work transitions?

Yes, the handoff process creates a dedicated handoffs directory to store standardized notes. This ensures expedition ship log updates and context handoffs are organized and committed to git.