agentleFS
skforecastskforecast/skforecast-ai/.claude/skills/handoff/SKILL.md

handoff

Skill52 starsChanged 47 days agoApache-2.0View on GitHub

Write a handoff document in dev/ so the work can continue in another session (cloud to local, local to cloud, another person, or a later session).

191 other projects use a version of this, 1 of them edited.

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 47 projects that use this

  • RoentekSkill

    loop-me

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

    Also in 59 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 105 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 101 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 62 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 2

    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. Very specific:

    Write dev/handoff_$ARGUMENTS.md (ask for a slug if none was given.

    line 10
  2. Distinctive:

    Keep it factual and short.

    line 29
  3. Distinctive:

    Do not commit it unless asked.

    line 31

“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 dev/handoff_$ARGUMENTS.md (ask for a slug if none was given; overwrite it if it already exists for this topic), in the language of the conversation:

  1. Title and one line of state: date, branch, and whether the changes are committed (and pushed) or only in the working tree.
  2. Goal and decisions: what we are trying to achieve and why each non-obvious decision was taken, including the options discarded and any measurements that supported them.
  3. Done: grouped by topic, with the public names and files that changed, and whether each block has tests and a release note in docs/releases/releases.md.
  4. Pending: for the author (review, commit, decisions, real-model runs) and for the next session, in order, each item concrete enough to start without rereading this conversation.
  5. Environment and verification: the exact commands to check the state (from /verify), and the result at the end of this session (test count, lint).

Keep it factual and short; link to files instead of copying code.

Do not commit it unless asked. In a cloud session it must reach the remote to be read elsewhere: commit it to the session branch together with the rest of the work, and remind the user to delete it before the pull request is merged. The handoff_ prefix tells it apart from the notes that dev/ versions on purpose; /open-pr keeps it out of the pull request.

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.