handoff

Generates a structured handoff document summarizing session state for the next agent.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill handoff-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/core/dependencies/review/handoff
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill handoff-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a working session ends or context runs out, critical state—decisions, verified evidence, repository status, and next steps—is easily lost, forcing the next agent or session to reconstruct everything from scratch. This Skill compacts the current conversation into a durable handoff document so a fresh agent can resume the exact work safely. ## Core Features & Use Cases - Structured Handoff Document: Produces a document with six required sections covering objective and status, repository state, verified evidence, decisions and constraints, the next safe action, and suggested skills. - Safe State Transfer: Saves the document to the OS temporary directory rather than the workspace, redacts sensitive information such as API keys and personal data, and references existing artifacts by path instead of duplicating them. - Use Case: Before ending a long debugging or implementation session, invoke the handoff skill so the next session receives the branch, dirty paths, verified command results, approved scope, and one concrete first action without re-reading the entire chat history. ## Quick Start Use the handoff skill to compact this session into a handoff document for the next agent to continue the repository migration work.

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 unfinished coding session to another AI agent?▼

Invoke the handoff skill at the end of your session. It writes a structured document covering objective, repository state, verified evidence, decisions, and the next safe action, saved to your OS temporary directory so a fresh agent can resume the work.

What should a session handoff document include?▼

A handoff document should include the objective and current status, repository state such as branch and dirty paths, verified evidence from commands run, decisions and constraints, one concrete next safe action, and the smallest set of suggested skills.

Where is the handoff document saved?▼

The document is saved to the temporary directory of the user's operating system, not the workspace. The skill reports only the file path after writing it.

Does the handoff document protect sensitive information?▼

Yes. The skill redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the document, and it references existing artifacts by path instead of duplicating their content.

When should I not rely on a handoff document alone?▼

Do not rely on it when durable records like PRDs, plans, ADRs, issues, or commits already capture the information. The handoff references those artifacts by path or URL rather than duplicating them, so those records must remain accessible.