Session Handoff

SkillDocs & knowledge

Lets your agent save a summary of current progress, decisions, and next steps so work can resume later.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Session Handoff skill

About this capability

Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".

What this skill tells your AI

The instructions your AI receives, as published by rohitg00/pro-workflow in skills/session-handoff/SKILL.md and read by ahel’s review.

Different from wrap-up. Wrap-up is a checklist for you. Handoff is a document written for the next session.

Trigger

Use when saying "handoff", "continue later", "pass to next session", "session transfer", or ending a session and wanting to resume smoothly.

Workflow

  1. Gather current state from git.
  2. List completed, in-progress, and pending work.
  3. Note key decisions made and their reasoning.
  4. Capture any learnings from this session.
  5. Generate a resume command for the next session.

Commands

git status
git diff --stat
git log --oneline -5
git branch --show-current

Output

# Session Handoff — [date] [time]

## Status
- **Branch**: feature/xyz
- **Commits this session**: 3
- **Uncommitted changes**: 2 files modified
- **Tests**: passing / failing / not run

## What's Done
- [completed task 1]
- [completed task 2]

## What's In Progress
- [current task with context on where you stopped]
- [file:line that needs attention next]

## What's Pending
- [next task that hasn't been started]
- [blocked items with reason]

## Key Decisions Made
- [decision 1 and why]
- [decision 2 and why]

## Learnings Captured
- [Category] Rule (from this session)

## Files Touched
- `path/to/file1.ts` — [what changed]
- `path/to/file2.ts` — [what changed]

## Gotchas for Next Session
- [thing that tripped you up]
- [non-obvious behavior discovered]

## Resume Command
> Continue working on [branch]. [1-2 sentence context]. Next step: [specific action].

Guardrails

  • Write for the reader (next session), not the writer.
  • Include specific file paths and line numbers where relevant.
  • The resume command should be copy-pasteable into the next session.
  • Keep it factual — describe changes functionally, don't infer motivation.

Signals

GitHub stars
3k
Forks
285
Last commit
Aug 2026
Advanced
Catalog kind
skill
Gateway key
session-handoff-rohitg00
Source
github.com/rohitg00/pro-workflow