From 8f3401d1a17ab65e92b18a6ad9d301e9addf135f Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Thu, 2 Jul 2026 11:24:51 +0100 Subject: [PATCH] claude-handoff: reuse original handoff wording Co-Authored-By: Claude Opus 4.8 (1M context) --- skills/in-progress/claude-handoff/SKILL.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/skills/in-progress/claude-handoff/SKILL.md b/skills/in-progress/claude-handoff/SKILL.md index 0e25b18..b326910 100644 --- a/skills/in-progress/claude-handoff/SKILL.md +++ b/skills/in-progress/claude-handoff/SKILL.md @@ -1,18 +1,16 @@ --- name: claude-handoff -description: Hand off the current conversation to a fresh background agent that picks up the work immediately. +description: Hand the current conversation off to a fresh background agent that picks up the work immediately. argument-hint: "What will the next session be used for?" disable-model-invocation: true --- -Compose a handoff summarising the current conversation so a fresh agent can continue the work, then launch it as a background agent seeded with that summary — do not save a document. +Write a handoff document summarising the current conversation so a fresh agent can continue the work. Instead of saving it, launch a background agent seeded with the document as its prompt: `claude --bg ""`. It starts in the current working directory and returns immediately; the user manages it with `claude agents`. -Launch with `claude --bg ""`, passing the summary as the prompt. It starts in the current working directory and returns immediately; the user manages it with `claude agents`. - -Include a "suggested skills" section in the summary, instructing the agent which skills to invoke. +Include a "suggested skills" section in the document, which suggests skills that the agent should invoke. Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead. -Redact any sensitive information, such as API keys, passwords, or personally identifiable information — it becomes the agent's prompt. +Redact any sensitive information, such as API keys, passwords, or personally identifiable information — the document becomes the agent's prompt. -If the user passed arguments, treat them as a description of what the next session will focus on and tailor the summary accordingly. +If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.