fleetd #480 Unit B: add handover skill for lead handoff #481
Reference in New Issue
Block a user
Delete Branch "worker/480-b-handover-skill-45bf1f-5"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds
.claude/skills/handover/SKILL.md: the procedure an outgoing lead follows to write the handover file a fresh lead session inherits when fleetd clears the pane (fleetd #480).The skill requires: every number carries the command that produced it (run in the writing turn); marking each claim as self-checked or reported by someone else; recording open decisions and who owns them; recording live hazards; recording what is explicitly not owed; opening the file with three re-measurement commands (role, tree state, live fleet); stamping the file with time and commit; telling the reader the file goes stale on any merge/spawn/restart; and a closing list of what to leave out (session narration, anything the repo already records, session-only advice).
Also registers the skill in CLAUDE.md's project addendum, under Primary-side skills (a worker cannot use it, since this is a lead-only handoff procedure). No other change to CLAUDE.md — the canonical block above the addendum is untouched (diffed to confirm).
This unit is documentation only: one new Markdown file, one two-line addition to CLAUDE.md's addendum. No Java changed, no dependency added, so
mvnwas not required and was not run.Studied
/Users/dai.ha/LTMS/.bridged-handover/HANDOVER.md(outside this worktree, read-only) as the one worked example, and generalized its structure rather than copying its content.