From 3f8c956325a00e585e6ea53ee214e8b228aefea8 Mon Sep 17 00:00:00 2001 From: Dai Ha Date: Fri, 11 Sep 2026 06:17:11 +0700 Subject: [PATCH] docs: the handover skill must not promise a tool that does not exist MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The skill shipped in #481 described fleetd #480's automation in the present tense: "fleetd ticket #480 lets a lead session hand off to a fresh one". The tool is not built. A session loading the skill would look for a fleet_handover tool it cannot call, and this repo already knows what a confidently wrong instruction costs — a wrong comment stops the reader investigating with a false conclusion, which is worse than no comment. Now says plainly: today the handoff is manual, #480 will automate the same cycle, and do not call fleet_handover because it does not exist. The nine procedure rules are unchanged — only who performs the swap changes when #480 ships, not what the file must contain. My wording to fix, not the worker's: the brief handed them the present tense. --- .claude/skills/handover/SKILL.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/.claude/skills/handover/SKILL.md b/.claude/skills/handover/SKILL.md index 5c08eb3..83001e7 100644 --- a/.claude/skills/handover/SKILL.md +++ b/.claude/skills/handover/SKILL.md @@ -1,13 +1,20 @@ --- name: handover -description: Procedure for an outgoing lead to write the handover file before a fresh lead session replaces it (fleetd #480). Load this when your context is full and fleetd is about to clear your pane. The file is the new lead's only inheritance — follow it exactly. +description: Procedure for an outgoing lead to write the handover file that a fresh lead session inherits. Load this when your context is filling up and you are about to be replaced, whether you hand off by hand or fleetd does it for you. The file is the new lead's only inheritance — follow it exactly. --- # Handover — write the file the next lead depends on -fleetd ticket #480 lets a lead session hand off to a fresh one. The outgoing lead writes a -handover file, fleetd checks it, clears the pane, and tells the new session to read that file -and carry on. +A lead session fills up its context and has to be replaced by a fresh one. The outgoing lead +writes a handover file, and the new session reads that file and carries on. + +**Today this is a manual handoff.** You write the file, then tell the operator where it is. The +operator starts the new session and points it at the file. + +**fleetd #480 will automate the same cycle** — the lead asks, fleetd checks the file, clears the +pane, and tells the fresh session to read it. That work is not shipped yet, so **do not call a +`fleet_handover` tool: it does not exist.** Check the live tool list before assuming otherwise. +Nothing else in this procedure changes when it does ship; only who performs the swap changes. **The new lead's only inheritance is that file.** It does not see your conversation, your plan, or your screen. If the file is thin or wrong, the new lead re-derives what you already knew, and