计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
in the summary. It starts in the current working directory and returns immediately; the user manages it with `claude agents`.\n\nAlways 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.\n\nInclude a \"suggested skills\" section in the summary, naming which skills the next agent should call the Skill tool for.\n\nDo not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.\n\nRedact any sensitive information, such as API keys, passwords, or personally identifiable information, since the summary becomes the agent's prompt.\n\nIf the user passed arguments, treat them as a description of what the next session will focus on and tailor the summary accordingly.\n","licenseDocuments":[]},"initialTranslation":{"id":"mattpocock-skills-skills-in-progress-claude-handoff","lang":"zh","description":"将当前对话交接给一个新的后台代理,该代理会立即接手工作。","model":"gpt-5-mini"}}
claude-handoff将当前对话交接给一个新的后台代理,该代理会立即接手工作。
AI 翻译
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Write a handoff summary of the current conversation so a fresh agent can continue the work. Save it to the temporary directory of the user's OS, then launch a background agent seeded with it as its prompt: claude --bg --name "<descriptive name>" -- "$(cat <summary file>)". Passing the file keeps the shell from running backticks or expanding $ in the 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 summary, naming which skills the next agent should call the Skill tool for.
Do not duplicate content already captured in other artifacts (specs, 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, since 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.