handoff

Generate HANDOFF.md and update CLAUDE.md with session context.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edri2or/ripo-skills-main --skill handoff-edri2or
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/edri2or/ripo-skills-main/tree/main/exported-skills/handoff
Command: npx skills add https://github.com/edri2or/ripo-skills-main --skill handoff-edri2or

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you capture and preserve session context across interactions by generating a structured HANDOFF.md and injecting a concise summary into CLAUDE.md, ensuring continuity between sessions.

Core Features & Use Cases

  • Create and update HANDOFF.md at the project root with a reflective diff of the session progress.
  • Inject a standardized session handoff into CLAUDE.md to survive context reloads.
  • Support handoff decisions, next steps, and status tracking across sessions.

Quick Start

Write or update HANDOFF.md for the current project and refresh CLAUDE.md with the latest session handoff.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve session context across Claude interactions?

You preserve session context by generating a structured HANDOFF.md at the project root and injecting a concise summary into CLAUDE.md. This captures current intent, decisions, and next steps to ensure continuity across sessions.

What is the best way to automate session handoffs for AI projects?

Automating session handoffs involves creating a reflective diff of session progress in HANDOFF.md and refreshing CLAUDE.md with the latest update. This ensures deterministic context preservation through clear change signaling.

How does injecting context into CLAUDE.md survive context reloads?

Injecting context into CLAUDE.md survives reloads by storing a standardized session handoff summary directly in the file. This makes current session intent and next steps available when the context window resets.

Do I need a specific project structure to use HANDOFF.md for memory tracking?

You need a standard project root directory where HANDOFF.md and CLAUDE.md can be created or updated. The skill operates at the project root to reflect current session status without requiring specialized folder structures.

Can I track decisions and next steps across multiple sessions?

You can track decisions and next steps across sessions by updating HANDOFF.md with a reflective diff of progress. This supports status tracking and ensures handoff decisions are preserved for future interactions.

Why does my session context get lost and how does a handoff file fix it?

Session context gets lost when context windows reset during reloads. A handoff file fixes this by capturing a structured summary of intent and decisions, ensuring deterministic updates and continuity between interactions.