handover

Generate a standardized markdown handover document with goals, status, blockers, and next steps.

2|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/intelligenttools-ai/fritz-ai-local --skill handover-intelligenttools-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/intelligenttools-ai/fritz-ai-local/tree/main/skills/handover
Command: npx skills add https://github.com/intelligenttools-ai/fritz-ai-local --skill handover-intelligenttools-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the loss of context and momentum that occurs when switching between different AI agent sessions or projects by creating a structured, actionable handover document.

Core Features & Use Cases

  • Knowledge Preservation: Automatically compiles pending captures and ingests session decisions, patterns, and facts into the brain before closing.
  • Structured Continuity: Generates a standardized handover document containing goals, status, blockers, and specific next steps for the next agent.
  • Use Case: When you need to stop working on a complex feature implementation, run this skill to ensure the next agent session knows exactly what was completed, what is blocked, and what the immediate next steps are without needing a manual summary.

Quick Start

Ask the agent to run the handover skill to save your current session state and generate a continuation document.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I preserve context when switching between AI agent sessions?

To preserve context when switching between AI agent sessions, you can generate a structured handover document. This markdown file compiles pending knowledge, session decisions, and specific next steps to ensure seamless continuity for the next agent.

What is the best way to transfer session state and pending tasks to a new agent?

The best way to transfer session state is to compile pending captures and ingest session decisions into a local brain registry. This process creates a standardized handover document with goals, status, blockers, and next steps for future reference.

How does a handover document help with complex feature implementation?

A handover document helps with complex feature implementation by recording what was completed, what is blocked, and immediate next steps. This prevents loss of momentum and eliminates the need for manual summaries when resuming work.

Do I need a local brain registry to generate a session handover document?

Yes, generating a session handover document requires integration with a local brain registry. The skill operates by ingesting session-specific decisions into this registry and adhering to a defined handover schema for task delegation.