handoff

Transfers a trailing work thread into a Jira ticket, git worktree, and tmux window with a written brief.

1|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/azaidrahman/zaid-sani-dotfiles --skill handoff-azaidrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/azaidrahman/zaid-sani-dotfiles/tree/main/dot_claude/skills/handoff
Command: npx skills add https://github.com/azaidrahman/zaid-sani-dotfiles --skill handoff-azaidrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When a Claude session ends with unfinished threads, the next session starts cold — re-reading logs, re-deriving theories, and asking you to repeat context. This Skill captures one trailing thread's findings in writing and spins up a ready-to-work environment so the new session opens warm. ## Core Features & Use Cases - Session Harvesting: Extracts established facts (with evidence), theories, ruled-out dead ends, touched files, and the next step from the conversation transcript. - Ticket and Branch Creation: Files a Jira ticket via the writing-tickets skill and creates a <type>/<KEY>-<slug> branch with a dedicated git worktree. - Warm Handoff Window: Writes a structured brief to ~/.claude/handoffs/<KEY>.md and opens a tmux window rooted in the worktree running Claude with that brief. - Use Case: You spent an hour debugging why HTTPRoutes stay OutOfSync and found the leading theory, but need to stop. Hand off the thread so a fresh window picks up exactly where you left off, with evidence intact. ## Quick Start Tell Claude to hand off the trailing thread about the OutOfSync HTTPRoutes into a new ticket and window.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off unfinished work between Claude sessions?

Invoke the handoff skill and name the trailing thread. It harvests the session's established facts and theories, files a Jira ticket, creates a worktree, writes a brief to ~/.claude/handoffs/, and opens a tmux window running Claude on that brief.

What goes into a session handoff brief?

The brief contains established facts with evidence, the leading theory plus rivals, ruled-out dead ends, touched files, the single next step, and verification criteria. Claims without evidence are moved to Theory so the next session can trust the file.

Does the handoff skill work without tmux?

The ticket, branch, worktree, and brief are still created without tmux, but no window opens. The script exits with code 3 and prints no-tmux; the skill then reports the brief path and the cd command so you can resume manually.

When should I use handoff instead of wrap-session?

Use handoff to carry exactly one trailing thread forward while leaving other open threads alone. Use wrap-session when you want to close out everything the session touched at once.

Why does handoff skip the EnterWorktree step?

The current session must stay in its existing checkout because the handoff opens a separate tmux window for the new work. That window starts in the worktree by itself, so switching the current session would be redundant.