handoffkit

Invoke the handoff skill explicitly, optionally with a focus argument describing the next session's goal. It scans the conversation, drafts a structured Markdown document with goal, state, next steps, and decisions, then saves it under docs/handoffs/ for the next agent to read.

Include the goal and why it matters, what is done versus open, the immediate next action, decisions with reasoning, ruled-out approaches, and how to run or verify. Reference existing artifacts like specs and PRs by path or URL instead of copying their contents.

No. Anything already written down, such as specs, ADRs, commit messages, diffs, and PR descriptions, is linked by path or URL rather than reproduced. The document only carries reasoning and state that exist solely in the conversation.

Yes. The skill redacts API keys, tokens, passwords, and personally identifiable information before output. Secrets are referred to by name only, such as the staging DB password in .env, never by value.

The skill degrades gracefully by emitting the finished handoff as a single Markdown code block in the chat and stating that no file was created. It also prints inline when the user explicitly requests terminal or copy-pastable output.

Model invocation is disabled so a session compaction never fires mid-work. It runs only when the user deliberately invokes it, ensuring the handoff captures a deliberate stopping point rather than interrupting active work.