agentleFS
Sign inStart free
RandyRawgustRandyRawgust/ai-knowledge-base-template/.claude/skills/handoff/SKILL.md

handoff

Skill1 starsChanged 6 months agoMITView on GitHub

Write a next-session handoff note before context runs out. Captures current state, what's done, what's mid-stream, and what to pick up first. Use when Andy says handoff, write a handoff, wrap up, context is running out, save state, end of session.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, setup-ts-deep-modules and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 93 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 87 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 51 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 54 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a structured next-session handoff so the next agent (or future-Andy) can resume cold without re-deriving context.

    line 8
  2. Very specific:

    Write to 00 - Chats/handoffs/<MM-DD-YY>-<slug>.md.

    line 21
  3. Very specific:

    If today's daily note exists, append to its ## Captures section: - [[<MM-DD-YY>-<slug>]] -- handoff

    line 60
  4. Distinctive:

    Don't dump the entire conversation - the handoff is a summary, not a transcript

    line 63
  5. Very specific:

    Don't skip the Recommended first move - that's the highest-value field

    line 64
  6. Distinctive:

    Don't write a handoff if the session was trivial (under ~5 substantive turns)

    line 65

“Common” is measured: kept by at least 6 in 10 of the 172 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Handoff

Write a structured next-session handoff so the next agent (or future-Andy) can resume cold without re-deriving context.

When to use

Triggers: handoff, write a handoff, wrap up the session, context is running out, save state, end of session, next session brief.

Load

  • CLAUDE.md - so the handoff respects vault conventions
  • 03 - Skills & Rules/Agents/Activity Log.md - last 5 rows for context
  • Current daily note 01 - Daily Notes/<today>.md if it exists
  • Any files the session has been editing (re-read for accurate current-state)

Output

Write to 00 - Chats/handoffs/<MM-DD-YY>-<slug>.md. Create the handoffs/ subfolder if missing.

Format:

---
type: handoff
created: <MM-DD-YY>
session_topic: <one-line>
status: <in-progress | done | blocked>
tags: [handoff]
---

# Handoff -- <topic>

## TL;DR
One paragraph: what we were doing, where we left off, what to do next.

## What got done this session
- <concrete change with file path>
- <...>

## Mid-stream (pick up here)
- <file or task half-finished, with line numbers / cursor location if relevant>
- <...>

## Blockers / open questions
- <thing that needs Andy's decision before next agent can proceed>

## Files touched
- <relative path> -- <one-line what changed>

## Recommended first move next session
The single most useful thing to do in the first 2 minutes of the next session.

After writing

  1. Provide [Open handoff](computer://...) link
  2. Append Activity Log row noting the handoff was written
  3. If today's daily note exists, append to its ## Captures section: - [[<MM-DD-YY>-<slug>]] -- handoff

Don't

  • Don't dump the entire conversation - the handoff is a summary, not a transcript
  • Don't skip the Recommended first move - that's the highest-value field
  • Don't write a handoff if the session was trivial (under ~5 substantive turns)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free