agentleFS
luizomfluizomf/omskills/skills/productivity/handoff/SKILL.md

handoff

Skill3 starsChanged 2 months agoMITView on GitHub

Write a handoff for a fresh agent. Save it under a unique Markdown filename in the OS temporary directory, outside the current workspace, and return the exact path. Include only continuation state that the referenced artifacts do not establish: - the current goal and immediate next step; - user intent, constraints, and preferences not recorded elsewhere; - decisions and reasoning not yet recorded in a durable artifact; - unresolved questions and blockers; - Delivery topology and Maintainer availability when the…

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

2 rules. 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a handoff for a fresh agent.

    line 10
  2. Very specific:

    If the user provides a next-session focus, order the established state required for that focus first without changing scope.

    line 35

“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 handoff for a fresh agent. Save it under a unique Markdown filename in the OS temporary directory, outside the current workspace, and return the exact path.

Include only continuation state that the referenced artifacts do not establish:

  • the current goal and immediate next step;
  • user intent, constraints, and preferences not recorded elsewhere;
  • decisions and reasoning not yet recorded in a durable artifact;
  • unresolved questions and blockers;
  • Delivery topology and Maintainer availability when the conversation resolved them but no cited durable artifact records them; and
  • relevant working-tree or external state that cannot be inferred safely from cited artifacts, including established decisions, the authorized stopping point, and recoverable state needed to continue while the maintainer is away.

Cite existing issues, specs, ADRs, documentation, commits, and diffs by path or URL instead of reproducing their content. Exclude tool logs, superseded exploration, and conversational transitions.

Include no recommendation, requirement, task, or follow-up that the conversation did not establish. A handoff preserves context only: it does not select a Ticket, grant Mission authorization, change availability, satisfy a Prompt Audit gate, or authorize implementation mutation.

If the user provides a next-session focus, order the established state required for that focus first without changing scope. Replace secrets with [REDACTED] and omit personal information that is not required for continuation.

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.