handoff

Summarizes the current conversation into a handoff document for a future agent session.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill handoff-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-core/skills/handoff
Command: npx skills add https://github.com/toderian/project_template --skill handoff-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Long agent sessions accumulate context that is lost when the session ends, forcing the next agent or teammate to re-read the entire transcript. This Skill compacts the conversation into a standalone handoff document so work can resume immediately in a fresh session. ## Core Features & Use Cases - Structured Session Summary: Captures goal, current state, key context, next step, and open questions in a single-screen Markdown document written to a tempfile path. - Reference-Based Handoff: Points to existing artifacts (PRDs, plans, ADRs, issues, commits) by path or URL instead of duplicating their content, and redacts secrets and personal data before writing. - Audience Tailoring: Adapts the handoff emphasis based on a free-text argument, such as "finish the migration" or "onboard a teammate", and suggests the skills the next session should invoke. - Use Case: At the end of a long debugging or implementation session, invoke the skill to produce a continuation note that a fresh agent can act on without any prior transcript. ## Quick Start Ask the agent to write a handoff document for the next session, optionally stating what that session will be used for.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off an AI agent session to a new session?

Invoke the handoff skill at the end of the session. It writes a Markdown document covering the goal, current state, key context, next step, and open questions to a tempfile path, which the next agent reads to resume work without the prior transcript.

What should a good session handoff document include?

A good handoff fits on one screen and contains the goal, current state, durable key context such as file paths and branch names, the single next action, and open questions or blockers. It references existing artifacts by path or URL rather than copying their content.

Does the handoff document copy plans and design docs into itself?

No. The handoff references durable artifacts like PRDs, ADRs, GitHub issues, and commits by path or URL instead of duplicating them. If a needed artifact does not exist yet, the gap is noted in the open questions section.

How are secrets and credentials handled in a handoff?

The skill redacts API keys, tokens, passwords, connection strings, and personal data before writing the document. It names the credential file path or environment variable instead of including the actual value, since handoffs are often saved outside the repo.

Can I tailor the handoff for a specific purpose like onboarding?

Yes. Pass a free-text argument describing what the next session is for. A handoff aimed at finishing a migration emphasizes state and next steps, while one aimed at onboarding a teammate emphasizes goal and key context.