session-handoff

Save session state and generate next-session.md for continuation.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/adiomas/claude-code-adiomas-plugins --skill session-handoff-adiomas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/adiomas/claude-code-adiomas-plugins/tree/main/autonomous-dev/skills/session-handoff
Command: npx skills add https://github.com/adiomas/claude-code-adiomas-plugins --skill session-handoff-adiomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures seamless continuity between consecutive /auto-execute sessions by saving the current state and preparing the next session to resume work without loss of context.

Core Features & Use Cases

  • End-of-session handoff: gracefully terminate the current session and archive breadcrumbs for the next run.
  • Context-awareness: detects approaching context limits and checkpoints progress for safe continuation.
  • Handoff artifacts: updates like next-session.md and progress records to guide future work.

Quick Start

Use the session-handoff skill at the end of a task to snapshot state and generate the next session context.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I save session state for seamless continuation across automated execution runs?

To save session state for seamless continuation, use this skill to snapshot progress and generate handoff artifacts. It updates tasks.json, progress.md, and state.yaml while creating next-session.md to guide future work.

What happens to my workflow when auto-execution hits context limits?

When auto-execution hits context limits, this skill detects approaching limits and checkpoints progress. It gracefully terminates the session, archives breadcrumbs, and prepares next-session.md for safe continuation.

How do I preserve task breadcrumbs when an automation session ends with errors?

To preserve task breadcrumbs when an automation session ends with errors, trigger this skill at session end. It captures the current state and logs progress into artifacts like progress.md and state.yaml.

Do I need external tools to manage session persistence and generate handoff files?

No external tools are required to manage session persistence and generate handoff files. This skill operates using only the repository's standard tooling to update state.yaml, tasks.json, and next-session.md.

What is the best way to hand off context between consecutive auto-execute sessions?

The best way to hand off context between consecutive auto-execute sessions is using this skill to update progress records and generate next-session.md. It ensures no context is lost between runs.

When should I trigger session handoff to snapshot state and prepare the next context?

Trigger session handoff to snapshot state at the end of a task, whether tasks are completed, context limits are reached, or errors occur. This preserves breadcrumbs for future work.