skills.rest
romiluz13
romiluz13COMMUNITY
Explore all skills by this author →
GitHub

session-handoff

Transfer active work between Pi sessions with a handoff document and intercom notification.

11|Updated Jul 2, 2026
Search Tags:#session handoff#project continuity#pi#intercom#context transfer#memory persistence
One-click install
npx skills add https://github.com/romiluz13/auto-pi --skill session-handoff-romiluz13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/romiluz13/auto-pi/tree/main/skills/session-handoff
Command: npx skills add https://github.com/romiluz13/auto-pi --skill session-handoff-romiluz13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill preserves essential project context when a Pi session is becoming too long, needs a fresh context window, or must transfer work to another session.

Core Features & Use Cases

  • Handoff Documentation: Captures active constraints, current progress, decisions, errors, and next steps in a durable handoff document.
  • Context Persistence: Saves architecture decisions, failures, corrections, and user preferences to memory for future sessions.
  • Session Coordination: Discovers compatible Pi sessions and notifies the selected recipient through intercom with the handoff location and next actions.
  • Use Case: Transfer an unfinished implementation from a nearly compacted project session to an available specialist session while preserving constraints and exact error messages.

Quick Start

Ask the session-handoff skill to hand off the current work to a fresh Pi session and notify the appropriate target.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I transfer project context to a fresh Pi session without losing progress?▼

To transfer project context to a fresh Pi session, this Skill captures active constraints, current progress, and next steps in a durable handoff document, then notifies the receiving session through intercom with the exact handoff location.

When should I use a session handoff for long-running tasks?▼

Use a session handoff when a long-running Pi session is nearing compaction, needs a fresh context window, or must transfer unfinished work to a specialist session while preserving architecture decisions, failures, and corrections.

What's the best way to preserve memory persistence across different Pi sessions?▼

The best way to preserve memory persistence across Pi sessions is by saving architecture decisions, failures, corrections, and user preferences to memory for future sessions before coordinating the handoff to a compatible recipient.

Can I transfer work across different project branches using session handoff?▼

Yes, you can transfer work across different project branches. This Skill applies to cross-project and cross-branch transfers by discovering compatible Pi sessions and notifying the selected recipient with the handoff location and next actions.

Do I need an intercom notification to coordinate a receiving session?▼

Yes, intercom notification is required. It coordinates the receiving session by sending the receiving Pi session the handoff document location and the exact next actions required to continue the work.

Related Skills

Explore More Software Engineering Skills→
forranyforrany

shared-memory

Save and load cross-session context under .claude/memory/sessions.

Community
Intermediate
nomoorynomoory
8

initiative-resume

Restore initiative context from a handoff document and index.yml.

Community
Advanced
vaaynevaayne
52

mori-agent-bridge

Coordinate agent-to-agent messaging and workflows across Mori panes.

Community
Advanced
eroslifestyleeroslifestyle
1

strategic-compact

Save session state to a structured Markdown checkpoint file.

Community
Basic