handoff

Creates handoff packets for agents, sessions, PR reviewers, or machines.

1|1|Updated Jul 24, 2014

Search Tags:#handoff #context preservation #PR comments #work transition #ignored artifacts

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of handoff work between agents, sessions, PR reviewers, or machines, ensuring continuity without leakage of sensitive information.

Core Features & Use Cases

Create Handoff Packets: Generate handoff packets for smooth transition of work to another agent or machine.
Handle Different Handoff Mediums: Supports handoffs via ignored artifacts, PRs, and durable repository docs.
Summarize Current State: Summarize the current state of work for the next agent, including goals, changes, decisions, and actions.

Quick Start

Generate a handoff for the current work using the handoff skill.

Frequently Asked Questions about handoff

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

FAQPage Schema

How do I create a work transition handoff for another agent or machine?▼

To create a work transition handoff, generate a handoff packet that summarizes current goals, changes, decisions, and actions for the next agent or machine to ensure continuity.

What is the best way to preserve context when handing off work via PR comments?▼

Preserving context via PR comments involves generating a handoff packet that summarizes the current work state, ensuring the next reviewer or agent has full continuity without secret leakage.

Can I use ignored artifacts to store handoff context for cross-machine transitions?▼

Yes, you can use ignored artifacts as a handoff medium to store transition context, allowing durable repository documentation that supports cross-machine work continuity.

Does generating a handoff packet expose secret values during work transition?▼

Generating a handoff packet does not expose secret values, because the process requires you to explicitly define the handoff medium and content to prevent sensitive information leakage.

What should be included in a handoff summary for the next agent?▼

A handoff summary should include current goals, recent changes, decisions made, and pending actions, providing the next agent with the necessary context to continue the work seamlessly.

When do I need to generate a durable repository handoff document?▼

You need a durable repository handoff document when transitioning work across sessions or machines and require a persistent, ignored artifact or PR comment to maintain local context.