19 lines
1.5 KiB
Markdown
19 lines
1.5 KiB
Markdown
---
|
|
name: claude-handoff
|
|
description: Hand the current conversation off to a background Claude Code session when the user chooses Claude for continuation.
|
|
---
|
|
|
|
Check `command -v claude` and the installed CLI's help for background-session support before launching. If unavailable, return the redacted handoff and explain the missing prerequisite; do not install software or switch agent products without the user's request.
|
|
|
|
Write a handoff summary so a fresh Claude session can continue the work. When supported by the installed CLI, launch it with `claude --bg --name "<descriptive name>" "<handoff summary>"` in the selected working directory. Use the CLI's reported session identifier and management commands; do not claim a session started if the command failed. Do not retry an ambiguous launch until checking whether it already created a session.
|
|
|
|
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 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 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 summary accordingly.
|