agentleFS
KealmanKealman/cland-v0/.agents/skills/handover/SKILL.md

handover

Skill1 starsChanged 17 days agoApache-2.0View on GitHub

Hand this session's Coordinator role or claimed Lead node to another session. Drafts the handover note in its four sections from the current work and calls `role.handover` through the cland spoke. Use when the human asks you to hand over, or when you must stop leading your node.

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 4 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

  • BlockSkill

    plan

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

    Also in 4 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 3 projects that use this

  • MicrosoftSkill

    caveman

    Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Write four sections in this order, none of them empty.

    line 29
  2. Very specific:

    If a section truly has nothing in it, say so in one line (Nothing waiting.).

    line 45
  3. Distinctive:

    If the human asked for the handover, show them the draft and apply their changes.

    line 47
  4. Very specific:

    Call the spoke tool role.handover with to and note.

    line 51
  5. Very specific:

    If the result has code: "invalid_argument", correct the named fields and retry (for example, supply the required note).

    line 53

“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

The next holder continues from the note and the hub. It never sees your transcript (spec 4.4, ADR 0001). Write the note so that a session which has seen none of this conversation can pick up the work.

1. Find the receiver

The argument names the session that takes the role. Call who. The receiver must be connected, or be a session launched through the hub (cland session list --json). The separate session.list read grant is held by every role by default; it grants no session lifecycle mutations.

  • A Coordinator asks the human when no receiver is named. If the human wants a fresh receiver, launch it with session.launch and give it no role; the role arrives with the handover.
  • A Lead's receiver must hold no item claim. If a receiver must be chosen or launched, send a question to lead T-<n> for your claimed node, naming the missing receiver; the question climbs to the supervising Lead or Coordinator.

Leads hand over their own claimed node; other Leads keep theirs.

2. Gather what the note rests on

Take the facts from the hub and the tracker, not from memory alone:

  • role.state: the topics waiting for the role, the open asks and the claims you hold. For a Lead, confirm its item and single node claim; state belongs to that node.
  • task.list for the open items and the ones assigned to or claimed by you, and task.view for the ones in flight.
  • history, plus history with a topic for each topic that is waiting.

3. Draft the note

Write four sections in this order, none of them empty. Keep the lines short. Name items by id (T-12), sessions by name and topics by id. Point at items, files and topics instead of copying them.

## Goals now
What your project or claimed node is driving at right now: the one to three outcomes the next holder steers toward.

## Work in flight
Each piece of work in your node that is moving: the item, who does it, where it stands, what comes next.

## Open decisions
What is still undecided, the options on the table, and who decides (the human through `ask`, or the Coordinator).

## Waiting on
What is blocked on someone else: the human, a Reviewer or QA verdict, a session's reply. Name who, and since when.

If a section truly has nothing in it, say so in one line (Nothing waiting.). The hub refuses an empty section.

If the human asked for the handover, show them the draft and apply their changes.

4. Hand over

Call the spoke tool role.handover with to and note. The note is the Markdown above, or an object with goals_now, work_in_flight, open_decisions and waiting_on. Pass then: "implementer" only when the human wants you to stay on as an Implementer.

  • If the result has code: "invalid_argument", correct the named fields and retry (for example, supply the required note). A supplied Markdown note or empty section may return { ok: false, code: "note-incomplete", missing }; fill in those sections and retry.
  • For any other refusal, tell the human what it says. Do not retry it another way.

5. Stop

When the handover succeeds, the hub sends you a "role revoked" event (with then, your Implementer clause instead). From that moment you no longer act in the handed-over role: no messages on its behalf, no item edits, no launches. The Coordinator's claims, or the Lead's node claim and default subscriptions, have moved to the new holder. Continue only in the role named by the new clause or on a new assignment.

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.