handoff

Package current work state into a structured handoff document for the next agent.

2|Updated Dec 8, 2018
One-click install
npx skills add https://github.com/indykish/dotfiles --skill handoff-indykish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/indykish/dotfiles/tree/main/skills/handoff
Command: npx skills add https://github.com/indykish/dotfiles --skill handoff-indykish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Package the current work state for the next agent to resume work.

Core Features & Use Cases

  • Captures scope/status, working tree, branch/PR/MR, CI status, running processes, tests, and next steps.
  • Supports handoffs across agents (Claude → Codex → OpenCode) or between sessions, especially for end-of-day wrap-ups or long-running tasks.
  • Provides a clear, repeatable structure to reduce context-switch friction and miscommunication during transitions.

Quick Start

Create a concise handoff digest by exporting scope, status, running processes, tests, and next steps for the incoming agent.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I package my current work state for the next agent to resume?

To package work state for an agent handoff, capture the current scope, working tree status, branch/PR/MR, CI status, running processes, tests, next steps, and risks into a structured document. This ensures the incoming agent resumes work with full context.

What is the best way to hand off a long-running task between Claude and Codex?

The best way to hand off long-running tasks between agents like Claude and Codex is to export a structured digest of the current scope, working tree, CI status, and next steps. This repeatable structure reduces context-switch friction and miscommunication during transitions.

How do I document git status and running processes for an end-of-day wrap-up?

Document git status and running processes for an end-of-day wrap-up by generating a handoff document that captures your branch/PR/MR details, test results, and next steps. This packages the working tree state so the next session resumes seamlessly.

Can I use tmux to capture running processes for a pull request handoff?

Yes, you can use tmux to capture running processes for a pull request handoff. The packaged handoff document captures running processes alongside CI status and working tree details, optionally augmented by scripts or references for extended context.

Do I need a SKILL.md file to generate a structured handoff document?

Yes, you need a valid SKILL.md frontmatter with name and description to generate a structured handoff document. This frontmatter provides the necessary metadata to package the work state and output the handoff context for the next agent.

What limitations exist when exporting work state across different coding agents?

When exporting work state across different coding agents, limitations depend on the captured context scope. The handoff package focuses on scope, working tree, CI status, and next steps, but may not capture uncommitted environmental nuances without optionally augmenting the output with scripts or assets.