session-handoff

Extract and transform conversation history into self-contained handoff prompts.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ARCASSystems/FounderOS --skill session-handoff-arcassystems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/ARCASSystems/FounderOS/tree/main/skills/session-handoff
Command: npx skills add https://github.com/ARCASSystems/FounderOS --skill session-handoff-arcassystems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to transfer and package the context of a conversation for continuation in a new session or with a different user, preserving decision rationale and context for accurate future action.

Core Features & Use Cases

  • Session Summarization: Automatically generate summaries of a conversation to facilitate easy transfer of context.
  • Contextual Continuation: Ensures a fresh session or a session with a new user picks up from where the last left off without losing essential details.
  • Type-A Handoff: Supports handoffs within the same project for the same user, retaining all project memory and installed skills.
  • Type-B Handoff: Transfers context to different users, ensuring external parties can continue without access to internal knowledge.
  • Type-C Prompt Creation: Creates self-contained prompts that can be pasted into any Claude session to continue work immediately.

Quick Start

To generate a handoff summary, use the command: 'summarize this for a new session'

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I transfer conversational context to a new session or a different user?▼

Transfer conversational context by extracting and packaging conversation history into a summarized format, preserving decision rationale and project details for accurate continuation by a new user or session.

What is the best way to maintain business process continuity across different chat sessions?▼

Maintain business process continuity by generating a session handoff summary that captures essential context, ensuring a fresh session picks up exactly where the previous one left off without losing critical project memory.

Can I create a self-contained prompt to continue project work in any Claude session?▼

Yes, you can create a self-contained prompt by packaging the current session's context and decision history, which can then be pasted into any new Claude session to resume work immediately.

How does cross-user handoff work for external parties without internal knowledge access?▼

Cross-user handoff works by transforming conversation history into a context package that external parties can use to continue the workflow, ensuring they have necessary details without requiring access to internal project knowledge.

What is the difference between a Type-A and Type-B session handoff?▼

A Type-A handoff retains project memory and installed skills for the same user within a project, while a Type-B handoff transfers context to different users, enabling external parties to continue without internal knowledge access.

Do I need to manually format conversation history for context transfer?▼

No, context transfer handles input parsing, context validation, and output formatting automatically through scripting, allowing you to easily extract and transform conversation history for handoffs.