agentleFS
L-X-TL-X-T/ng-agentic-skills/.agents/skills/handover/SKILL.md

handover

Skill13 starsChanged 44 days agoMITView on GitHub

Compact the current conversation into a handover document for another agent to pick up. Use when the user wants to hand work over to a new session, says "handover", "hand off", or asks to summarise the session for the next agent.

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use harness-init, incident 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.
  • steptianSkill

    harness-init

    初始化 .harness 开发框架,集成代码修改影响范围评估和测试覆盖建议功能。触发词:'初始化新项目'、'harness init'、'更新 harness'、'分析影响范围'、'评估修改影响'

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 4 projects that use this

  • GoogleSkill

    to-tickets

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    Also in 4 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 4 projects that use this

  • +2 more from google

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 40 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. Distinctive:

    Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs).

    line 17
  2. Distinctive:

    If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

    line 19
  3. Very specific:

    If the next session involves implementation, prototyping, architecture, or documentation, mention that the agent should follow …

    line 21

“Common” is measured: kept by at least 6 in 10 of the 40 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

Handover

Write a handover document summarising the current conversation so a fresh agent can continue the work. Save it to a fresh temp file: run f=$(mktemp "${TMPDIR:-/tmp}/handover.XXXXXX") && mv "$f" "$f.md" && echo "$f.md" and write to the printed path. The trailing XXXXXX is the only template BSD and GNU mktemp both expand, so the random part must sit at the end before the rename; never leave a literal XXXXXX in the filename.

Suggest the skills to be used, if any, by the next session – pick from the catalogue in 02-SKILLS.md rather than guessing names.

Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

If the next session involves implementation, prototyping, architecture, or documentation, mention that the agent should follow style-guide/style-guide.md and load the relevant specific guide.

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.