handoff

Update session.md with completed tasks, pending work, blockers, and learnings.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/agent-core --skill handoff-ddaanet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ddaanet/agent-core/tree/main/skills/handoff
Command: npx skills add https://github.com/ddaanet/agent-core --skill handoff-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The handoff skill updates session.md with completed tasks, pending work, blockers, and learnings to ensure seamless agent continuation.

Core Features & Use Cases

  • Update session.md with standardized handoff notes following the template.
  • Capture context across Completed, Pending, Blockers, and Learnings for next agents.
  • Optional --commit tail-call to /commit for atomic commit and transition.

Quick Start

Invoke the handoff skill to persist session context and prepare the next agent. Example: Use /handoff to perform the handoff, optionally appending --commit to commit changes.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer agent context and pending tasks to another agent?

Session handoff works by writing context-rich notes categorized into Completed, Pending, Blockers, and Learnings sections into session.md, allowing the next agent to resume work with full historical context.

What is the best way to document agent learnings and blockers for future sessions?

Use the handoff skill by invoking /handoff to persist session context into session.md. Optionally append --commit to tail-call /commit for atomic commit and transition of the changes.

Can I automatically commit session.md changes when performing an agent handoff?

Yes, the handoff skill works in multi-agent workflows by applying a standardized handoff template that transfers completed tasks, pending work, blockers, and learnings across planning, execution, and review phases.

When do I need to update session.md for multi-agent workflows?

The handoff skill has no explicit dependencies and requires only a session.md file to write to, making it suitable for any multi-agent workflow environment without additional setup.