agentleFS
Sign inStart free
BSSE23047BSSE23047/nauraiz-dev/skills/handoff/SKILL.md

handoff

Skill2 starsChanged 14 days agoMITView on GitHub

Write or refresh the session handoff before stopping, compacting or switching machines: goal, done, next, open questions, files in play. Use when asked to hand off, wrap up, or when the PreCompact/Stop reminder appears. Not a commit or PR step.

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

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Leave the next session (or the next machine) a record it can start from.

    line 9
  2. Distinctive:

    Never invent a "done" item: list only what a commit, a changed file or the conversation shows.

    line 17
  3. Very specific:

    Write absolute dates (2026-10-30), never "today" or "yesterday".

    line 19
  4. Very specific:

    Keep it short. The next session reads the first 20 lines of session.md, so put the goal, done and next first.

    line 21
  5. Very specific:

    Run git branch --show-current, git status --short and git log --oneline -10.

    line 26
  6. Very specific:

    Read .claude/nauraiz-dev.json for state and plan.dir.

    line 27
  7. Very specific:

    Write the handoff last, by state, so it is the newest file written:

    line 46

“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

Leave the next session (or the next machine) a record it can start from. The shape of session.md and one filled example: run node "${CLAUDE_PLUGIN_ROOT}/scripts/show.mjs" skills/handoff/reference.md (never Read plugin files directly; a project hook may deny reads outside the repo).

Rules for every step:

  • Facts come from git status --short, git log --oneline -10 and this conversation. Never invent a "done" item: list only what a commit, a changed file or the conversation shows.
  • Write absolute dates (2026-10-30), never "today" or "yesterday". Today's date is in your context; if it is not, ask.
  • Keep it short. The next session reads the first 20 lines of session.md, so put the goal, done and next first.

Steps

  1. Run git branch --show-current, git status --short and git log --oneline -10. Read .claude/nauraiz-dev.json for state and plan.dir; if there is a .claude/nauraiz-dev.local.json, it overrides. Then read the existing handoff file (step 4 says which one), and for scaffold also .claude/state/backlog.md and .claude/state/completed.md, before writing anything.
  2. Draft the five parts from the facts: goal, done, next (the very next step first), open questions, files in play (paths from git status, plus files the conversation centred on). Carry over anything still true from the existing handoff; drop what is stale.
  3. scaffold only, for backlog and completed (do this before step 4):
    • A backlog.md item is finished only if the conversation or a commit shows it. Move it to the top of completed.md as ## YYYY-MM-DD — Title, a one-line summary, and the files or commit hashes touched (the format in the file's own header). Remove it from backlog.md.
    • Unsure whether an item is finished: ask the user. Do not move it on a guess.
    • Work that surfaced and is not started goes into backlog.md as a ## Title heading with one line of context.
  4. Write the handoff last, by state, so it is the newest file written:
    • scaffold: rewrite .claude/state/session.md in full with the five headings from reference.md. Rewriting the file also refreshes its mtime, which is what the PreCompact and Stop reminders compare against the last edit.
    • none: find the plan: the .md file under plan.dir (default .work/tasks) whose frontmatter branch: equals the current branch. Rewrite only its ## Handoff section, leaving ## Scope, ### Allowed and every other section untouched. Start the section with the absolute date and a colon, as the plan template does.
    • none and no plan matches the branch, or no config file: write .work/handoff.md with the five parts, and say you did.
  5. Print what you wrote and where, and the one line "Next: ...". Do not commit, push or open a PR; that is a separate step the user asks for.

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