skills.rest
cilerler
cilerlerCOMMUNITY
Explore all skills by this author →
Website𝕏@cilerlerGitHub

session-handoff

Generates a structured end-of-session summary so a fresh agent can resume work after context is cleared.

2|1|Updated Feb 12, 2026
Search Tags:#ai agent#workflow continuity#session handoff#session summary#context handoff#wrap up
One-click install
npx skills add https://github.com/cilerler/lillian --skill session-handoff-cilerler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/cilerler/lillian/tree/main/plugins/ai-toolkit/skills/session-handoff
Command: npx skills add https://github.com/cilerler/lillian --skill session-handoff-cilerler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a long AI-assisted work session ends and the conversation context is cleared, all decisions, running processes, and in-progress state are lost. This Skill produces a complete, chat-only handoff summary so the next agent session can continue without re-discovery. ## Core Features & Use Cases - Fixed Output Template: Produces a consistent structure covering decisions, shipped changes, key files, running state, verification commands, deferrals, and open questions. - State Capture Rules: Pulls from plan files, task lists, background process IDs, and files touched during the session, with absolute paths and explicit "none" markers for empty sections. - Use Case: Before clearing a long debugging session, ask for a handoff and receive a summary listing the dev server port, background process handles, modified files, and the single next action for a fresh agent. ## Quick Start Ask the agent to wrap up the session and produce a session handoff summary before you clear the conversation context.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I hand off an AI coding session before clearing context?▼

Ask the agent for a session handoff or to wrap up the session. It reviews the full conversation and produces a structured chat summary covering decisions, key files, running state, verification commands, and the next action for a fresh agent.

What should an end-of-session handoff summary include?▼

A handoff should include decisions made, files changed with absolute paths, background process IDs and how to stop them, dev server ports, verification commands, deferred items, open questions, and one clear next action.

Does the session handoff write a file or update memory?▼

No. The handoff is chat-only by design. It never writes to a file, never updates memory, and never audits the filesystem with git log or broad file searches. It only synthesizes what happened in the current session.

When should I use documentation-generator instead of session handoff?▼

Use documentation-generator with its takeover-handover template when you need a long-form project or role handover document. Use session handoff for a quick chat-only summary before clearing conversation context.

Why does the handoff require absolute paths and process IDs?▼

The next agent may have a different working directory and cannot discover background processes on its own. Absolute paths and process handles with stop commands ensure the fresh agent can locate files and manage running state immediately.

Related Skills

Explore More Software Engineering Skills→
Thanh-aperoThanh-apero
1

watzup

Summarize recent commits and analyze their impact in the current branch.

Community
Basic
wangke19wangke19
1

session-init

Resume coding sessions from .ai-session/STATE.md checkpoints or start fresh.

Community
Advanced
BRANDNEWSHVTBRANDNEWSHVT

persistent-memory

Automate persistent memory across AI agent sessions using file-based storage.

Official
Advanced
aemsitesaemsites
1

handover

Generate structured handover documentation for Edge Delivery Services projects.

Official
Advanced