session

Preserve and restore user context across Claude Code sessions.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/xavierfuentes/executive-assistant-framework --skill session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session
Source: https://github.com/xavierfuentes/executive-assistant-framework/tree/main/.claude/skills/session
Command: npx skills add https://github.com/xavierfuentes/executive-assistant-framework --skill session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides seamless continuity across Claude Code conversations by preserving, restoring, and handing off context between sessions despite timeouts, closures, or transitions.

Core Features & Use Cases

  • Context preservation: Captures the decision history, in-progress work, and key context to resume where you left off.
  • Context restoration: Reconstructs the active context at session start to create a smooth continuation.
  • Session handoffs: Generates a handoff-ready state for transfer between devices or teammates.
  • Session summaries: Produces concise summaries of current state and next steps to keep momentum.

Quick Start

  • Start a session with /resume to restore prior context.
  • End a session with /preserve to save progress and decisions.
  • Use /handoff to transfer context to another device or collaborator.
  • Request a Context Summary to reorient at any time.

Frequently Asked Questions about session

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

FAQPage Schema
How do I preserve and restore context across Claude Code sessions?

To preserve and restore context across Claude Code sessions, use /preserve at session end to save decisions and in-progress work, then /resume at the next session start to reconstruct the active context and continue seamlessly.

What is session handoff and when do I need it for context continuity?

Session handoff generates a handoff-ready state that transfers preserved context, decision history, and priorities between devices or teammates. You need it when transitioning active work to a new collaborator or environment without losing momentum.

How do I resume a Claude Code session after a timeout or closure?

To resume a Claude Code session after a timeout or closure, start a new session with /resume. The skill reconstructs your prior context from memory graph access, actions.md, and session-handoff records to create a smooth continuation.

Do I need memory graph access and actions.md to generate context summaries?

Yes, generating concise context summaries and transitions requires memory graph access, actions.md, and session-handoff records. These inputs capture decision history and ongoing priorities needed to reorient and maintain session continuity.

Can I transfer context between teammates during a session handoff?

Yes, you can transfer context between teammates by using /handoff to generate a handoff-ready state. This preserves the decision history, in-progress work, and key context so another collaborator can resume with full continuity.

What's the best way to reorient and surface ongoing priorities mid-session?

The best way to reorient mid-session is to request a Context Summary. This produces a concise summary of the current state and next steps, leveraging memory graph data to surface ongoing priorities and maintain momentum.