handoff

rohitg00/agentmemory

Resume the most recent agent session for your project, picking up from any unanswered question.

What is handoff?

Handoff retrieves and resumes the most recent agent session for the current working directory, leading with any open questions. Use it when the user says "where were we", "resume", or starts a session with no fresh context.

Matches sessions by directory boundary to avoid confusing sibling repositories
Surfaces unanswered user-facing questions first when resuming
Summarizes key files, decisions, and errors from the previous session
Provides a concrete next-step pointer to continue work
Accepts optional cwd override to resume sessions in other directories

How to install handoff

npx skills add https://github.com/rohitg00/agentmemory --skill handoff

Prerequisites

agentmemory installed and configured
memory_sessions and memory_recall functions available

Claude Code

Cursor

Windsurf

Cline

How to use handoff

1.Invoke the skill when you want to resume work (e.g., user says 'resume' or 'where were we')
2.Optionally pass a cwd override argument to resume a session in a different directory
3.The skill resolves the project path and queries the most recent matching session
4.Review the surfaced unanswered question (if any) and the session summary
5.Follow the concrete next-step pointer to continue work

Use cases

Good for

User returns to a project after a break and asks 'where were we?'
Resuming work on an authentication feature with an open design question
Picking up a multi-file refactor that was paused mid-session
Continuing a debugging session where the root cause was identified but not yet fixed
Switching between projects and needing to recall context for the current one

Who it's for

Developers working on multi-session projects
Teams using agent-assisted coding with memory persistence
Anyone resuming interrupted work and needing quick context recall

handoff FAQ

What if there are multiple sessions for the same directory?

The skill picks the most recent session, preferring completed sessions over abandoned ones.

Can I resume a session from a different directory?

Yes, pass an optional cwd override argument to the skill to resume a session in another directory.

What happens if there's no matching session for my project?

The skill falls back to the single most recent session overall and reports it plainly, offering to start fresh.

How does the skill avoid confusing sibling repositories?

It uses directory-boundary matching (exact equality or path separator checks) rather than raw prefix matching, so /repo-a-staging won't be confused with /repo-a.

What if the previous session ended with no unanswered question?

The skill summarizes key files, decisions, and errors from the session and provides a next-step pointer based on the work completed.

Full instructions (SKILL.md)

Source of truth, from rohitg00/agentmemory.

name: handoff description: Resume the most recent agent session for the current working directory, leading with any unanswered question. Use when the user says "where were we", "resume", "handoff", "pick up where I left off", or starts a session with no fresh context. argument-hint: "[optional cwd override]" user-invocable: true

The user wants to resume work. Optional cwd override: $ARGUMENTS

Quick start

memory_sessions { "limit": 20 }

Pick the most recent session whose cwd matches this project, then: memory_recall { "query": "<session top concepts>", "limit": 10 }.

Expected output:

Resuming 7f3a9c2 "Auth refresh rework".
Open question: should logout revoke all device tokens or just the current one?
Next step: decide revoke scope, then update auth/logout.ts.

Why

Match the session by directory boundary, not raw prefix, so a sibling repo never gets mistaken for this one. Never invent observations for an empty session.

Workflow

Resolve the project path: if $ARGUMENTS is given, normalize it to absolute (path.resolve(process.cwd(), $ARGUMENTS)); else use the cwd.
Call memory_sessions. Pick the most recent session whose normalized cwd matches by directory boundary: equality, OR cwd.startsWith(projectPath + sep), OR projectPath.startsWith(cwd + sep). Prefer completed over abandoned. No match: fall back to the single most recent session overall.
If the session ended on an unanswered user-facing question, surface it FIRST. Look in summary or recent conversation observations whose narrative ends in ?.
Summarize: title/summary, key files, key decisions or errors, using memory_recall on the top concepts, limit 10.
End with one concrete "next step?" pointer.