agentleFS
Sign inStart free
MagicJoshMagicJosh/ras/skills/handoff/SKILL.md

handoff

Skill1 starsChanged 9 days agoMITView on GitHub

Use when the user types /handoff to pass the current work to a fresh session, a colleague or another agent. Writes one handoff file under .ras/handoffs/ and changes no other project file.

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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write one file that lets a reader who never saw this conversation continue the work.

    line 9
  2. Very specific:

    If the user named the next goal, such as /handoff review the plan, shape the file around that goal.

    line 13
  3. Distinctive:

    Write these sections. Keep each one short and concrete.

    line 14
  4. Distinctive:

    Leave out secrets, tokens, passwords and personal data.

    line 26
  5. Distinctive:

    Write for a reader who knows the tools but not this project.

    line 27

“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 one file that lets a reader who never saw this conversation continue the work.

Steps

  1. If the user named the next goal, such as /handoff review the plan, shape the file around that goal.
  2. Write these sections. Keep each one short and concrete.
    • Goal: what the work is for, in one or two sentences.
    • State: what is done, what is in progress and what has not started. Name the branch and the last commit.
    • Decisions: each settled choice and its reason, one line each.
    • Open questions: each open choice, with your recommended answer.
    • Next steps: a numbered list. The reader can do step 1 without asking anything.
    • Pointers: the files, specs, commits, issues and commands that matter, by path or link.
  3. Save the file as .ras/handoffs/<date>-<topic>.md in the project root. Use the Write tool, which creates the folder. If .ras/handoffs/.gitignore does not exist, create it with one line: *. That keeps every handoff out of git. Never edit the project's own .gitignore. Give the full path of the handoff file. If you cannot write there, print the file in your reply.

Rules

  • Point to a file, a spec or a commit by its path. Do not copy its content.
  • Leave out secrets, tokens, passwords and personal data.
  • Write for a reader who knows the tools but not this project.
  • Mark what you did not check. Do not state a guess as a fact.

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.

Reviews can't be read right now.

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