skills.rest
arvidfcjarfalla-prog
arvidfcjarfalla-progCOMMUNITY
Explore all skills by this author →
GitHub

handoff

Save current session state to a dated handover file with structured frontmatter.

Updated Mar 12, 2026
Search Tags:#workflow#documentation#handoff#session-management#context-persistence#cross-session
One-click install
npx skills add https://github.com/arvidfcjarfalla-prog/atlas --skill handoff-arvidfcjarfalla-prog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/arvidfcjarfalla-prog/atlas/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/arvidfcjarfalla-prog/atlas --skill handoff-arvidfcjarfalla-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save the current session's state so the next session can continue seamlessly.

Core Features & Use Cases

  • Write handover file to .claude/handovers/YYYY-MM-DD_HHMM.md with frontmatter including date, goal, status, and files_changed.
  • Include a detailed handover template covering goal, accomplishments, decisions, remaining work, known issues, and explicit file-change evidence.
  • Update learned-rules.md if new rules are discovered.
  • Report the handover file path to the user.

Quick Start

Create a dated handover file at .claude/handovers/YYYY-MM-DD_HHMM.md summarizing the current session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I save session state to resume work after a break?▼

You preserve session state by writing a dated handover file to .claude/handovers/YYYY-MM-DD_HHMM.md using a structured template that captures the goal, status, and changed files for seamless cross-session continuity.

What is a handover file and what should it include for session continuity?▼

A handover file is a markdown document with frontmatter that records the date, goal, status, and files changed, along with a detailed template covering accomplishments, decisions, remaining work, and known issues for cross-session continuity.

When should I create a handover document for my workflow?▼

Create a handover document when ending a long session, before taking a break, or when the context becomes lengthy, ensuring the next session can resume seamlessly with full status awareness.

How do I document changed files and known issues before ending a session?▼

Use a structured handover template to document explicit file-change evidence, known issues, remaining work, and decisions, saving the output to a timestamped markdown file under the .claude/handovers directory.

Can I persist learned rules and context across different sessions?▼

Yes, session management includes updating a learned-rules.md file if new rules are discovered during the session, ensuring context persistence and rule enforcement across future cross-session work.

Related Skills

Explore More Content & Communication Skills→
ebal5ebal5

handover

Generate HANDOVER.md files with decisions, pitfalls, lessons, and next actions.

Community
Intermediate
jackspacejackspace
16

session-launcher

Restore session state and project context into a structured HTML dashboard.

Community
Intermediate
manastalukdarmanastalukdar
1

session-update

Append timestamped progress, git status, and branch info to a session file.

Community
Basic
tanujsutariatanujsutaria
1

session-checkpoint

Validate iOS build status, inspect Git changes, and assess session goals.

Community
Intermediate