session-handoff

Topics in the source

• Handoff
• Invocation Triggers
• First-Run Setup
• Output Path
• Section Template
• The Agent's Job
• Anti-Patterns
• Redaction

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS — not the current workspace. 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. If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly. Explicit phrases (any of): "hand this off" "handoff doc" "summarize this for a new session" "compact this conversation" "I'm ending this session" "pick this up later" "wrap this up for tomorrow" "save this for the next session" Implicit signals (no phrase, but the intent is unmistakable): User announces they're switching machines or stopping for the day mid-task Conversation context is growing long without a natural stopping point User says "let me come back to this" or "I'll continue this later" When you detect an implicit trigger

This is an excerpt. Refer to the complete source and its current requirements.