handoff-protocol

Record task state in HANDOFF.md, SESSION.md, and WORKLOG.md for agent handoffs.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/asadbek21coder/sinfim --skill handoff-protocol-asadbek21coder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-protocol
Source: https://github.com/asadbek21coder/sinfim/tree/main/frontend-vue/.claude/skills/handoff-protocol
Command: npx skills add https://github.com/asadbek21coder/sinfim --skill handoff-protocol-asadbek21coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The handoff protocol preserves active work context across agents by recording state and decisions in repository files, reducing reliance on chat history and preventing loss of progress.

Core Features & Use Cases

  • Persistent task context stored in SESSION.md, HANDOFF.md, and WORKLOG.md to enable seamless continuation.
  • Structured handoffs with clear summaries, touched files, decisions, and concrete next steps.
  • Agent-switch coordination supports Claude and Codex handoffs across sessions and tools.

Quick Start

Use the handoff protocol at task completion to snapshot the current state into HANDOFF.md and prepare the next agent for continuation.

Frequently Asked Questions about handoff-protocol

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

FAQPage Schema
How do I preserve task context across multi-agent AI sessions?

To preserve task context across multi-agent AI sessions, record active work state, decisions, and touched files in repository files like HANDOFF.md and SESSION.md, preventing progress loss during agent switches.

What is the best way to coordinate handoffs between Claude and Codex?

The best way to coordinate handoffs between Claude and Codex is to use a structured handoff protocol that snapshots the current state into HANDOFF.md, ensuring seamless continuation across tools and sessions.

How do I track progress and next steps for long-running tasks across different agents?

Track progress and next steps for long-running tasks by maintaining a WORKLOG.md file in your repository, which records decisions, progress, and concrete next steps to guide the next agent.

When do I need a handoff protocol for my AI workflow?

You need a handoff protocol for your AI workflow when managing long-running, multi-session tasks where decisions, progress, and next steps must survive agent switches rather than relying on chat history.

Does the handoff protocol work without external dependencies?

Yes, the handoff protocol works without external dependencies because it enforces functional requirements by recording state directly in repository files like HANDOFF.md, SESSION.md, and WORKLOG.md.