skills.rest
garyj
garyjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

handoff

Generate a detailed handoff plan preserving conversation context for new agent sessions.

Updated Dec 1, 2023
Search Tags:#workflow#documentation#handoff#knowledge-transfer#context-preservation#session-continuation
One-click install
npx skills add https://github.com/garyj/dotfiles --skill handoff-garyj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/garyj/dotfiles/tree/main/home/dot_agents/skills/handoff
Command: npx skills add https://github.com/garyj/dotfiles --skill handoff-garyj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a detailed handoff plan to preserve conversation context when transitioning to a new agent session.

Core Features & Use Cases

  • Captures explicit purpose, decisions, and next steps for continuity across agents.
  • Documents key technical details, references, and context to enable smooth resumption of work.
  • Use case: ending a current session and handing off to another agent or human collaborator to continue the task without context loss.

Quick Start

Provide the purpose or context for the handoff to generate a detailed continuation plan.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve conversation context when handing off work to a new agent session?▼

To preserve conversation context for session continuation, generate a detailed handoff plan that captures technical details, file references, and decisions. This plan ensures seamless continuation across sessions without context loss.

What is the best way to document knowledge transfer for delegating tasks to another agent?▼

Knowledge transfer for task delegation is best handled by producing a structured handoff plan. This plan documents explicit purpose, key decisions, and next steps to enable smooth resumption of work by another agent or human collaborator.

What should I include in a session handoff plan to avoid losing technical details?▼

A session handoff plan should include explicit purpose, key technical details, file references, decisions, and next steps. Capturing these elements ensures technical context is preserved for the next agent session.

When do I need to generate a handoff plan for workflow continuation?▼

You need to generate a handoff plan when ending a current session or delegating tasks to another agent. It ensures technical details and context are captured for seamless continuation across sessions.

Can I use a handoff plan to delegate work to a human collaborator instead of another agent?▼

Yes, a handoff plan can delegate work to either another agent or a human collaborator. It captures the purpose, decisions, and context required for smooth resumption of work without context loss.

Does generating a handoff plan require any specific dependencies or environment setup?▼

No specific dependencies or environment setup are required to generate a handoff plan. Simply provide the purpose or context for the handoff to produce a detailed continuation plan with structured metadata fields.

Related Skills

Explore More Content & Communication Skills→
pragsmikepragsmike
4

handoff

Generate structured session handoff documents for successor AI agents.

Community
Intermediate
MINT-IAMINT-IA

gsd-resume-work

Restore project session context from STATE.md and checkpoint files.

Official
Advanced
robynsmithrobynsmith

handoff

Capture git state, timestamps, and session details into structured handoff documents.

Community
Advanced
boshu2boshu2
418

handoff

Generate structured handoff documents and continuation prompts from Git history and .agents content.

Community
Basic