handoff

Append structured journey summaries of recent work to preserve conversation context.

2|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill handoff-is-ivanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill handoff-is-ivanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents important session knowledge from being lost between conversations by capturing notable decisions, surprises, mistakes, and codebase quirks in a structured handoff summary.

Core Features & Use Cases

  • Journey Summary Capture: Reviews work since the last recorded work-unit commit and logs only noteworthy moments.
  • Idempotent Recording: Avoids duplicate entries even when run multiple times during the same conversation.
  • Carryover Promotion: Moves lasting quirks and invariants from completed story scenarios into carryover notes for future sessions.
  • Use Case: When wrapping up a debugging or implementation session, use this Skill to preserve the context a future agent would need before clearing conversation history.

Quick Start

Ask the agent to run the handoff skill before clearing context so it records any notable decisions, surprises, and carryover from the current work item.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve conversation context before clearing session history?

Workflow continuity is maintained by appending structured journey summaries that automatically capture notable decisions, debugging discoveries, and codebase quirks from your session. This prevents important context loss between conversations when clearing history.

Can I avoid duplicate summary entries when running handoff multiple times?

Yes, the Skill avoids duplicate summary entries through idempotent recording. It writes append-only journey summaries that prevent duplication even when run multiple times during the same conversation or session wrap-up.

What's the best way to capture debugging discoveries and codebase quirks for future work?

The best way to capture debugging discoveries and codebase quirks for future work is to use automatic journey summary capture. This Skill reviews activity since the last work-unit commit and logs only noteworthy moments, promoting lasting invariants into carryover files for future sessions.

Does session wrap-up require locating a specific work item before generating a journey summary?

Yes, session wrap-up requires locating the active work item first. The Skill reviews activity since the last recorded work-unit commit to accurately capture context preservation data and generate a reliable journey summary for your task.

When should I not use automated context preservation for workflow continuity?

You should avoid automated context preservation when your active work item has no new activity since the last work-unit commit. Without recent notable decisions, mistakes, or codebase quirks, the Skill will not generate meaningful journey summaries or carryover entries for workflow continuity.