arda/skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

claude-handoff: say handoff summary, not document

Browse source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock 2026-07-02 11:26:55 +01:00
parent 8347a41614
commit 5a7ee93f01
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
skills/in-progress/claude-handoff/SKILL.md
View file

@ -5,14 +5,14 @@ argument-hint: "What will the next session be used for?"
disable-model-invocation: true
---
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 --name "<descriptive name>" "<handoff document>"`. It starts in the current working directory and returns immediately; the user manages it with `claude agents`.
Write a handoff summary of the current conversation so a fresh agent can continue the work. Instead of saving it, launch a background agent seeded with the summary as its prompt: `claude --bg --name "<descriptive name>" "<handoff summary>"`. It starts in the current working directory and returns immediately; the user manages it with `claude agents`.
Always pass `-n`/`--name` with a descriptive name (e.g. `--name "Fix login bug"`) — it sets the display name shown in the job list, session picker, and terminal title.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Include a "suggested skills" section in the summary, 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 — the document becomes the agent's prompt.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information — the summary 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 doc accordingly.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the summary accordingly.