| name | nmem-thread-handoff |
| description | Save a concise Google Antigravity handoff summary only when the user explicitly asks. This is intentionally separate from full thread-save, which should use the native session importer script. Triggered by /nmem-thread-handoff. |
Save Handoff
Only use this skill when the user explicitly asks to save progress as a handoff, leave a resumable summary, or create a lightweight restart point.
Why This Is A Handoff
nmem-save-thread should mean saving the real session messages through the custom session importer script.
This skill intentionally creates a structured handoff summary thread instead of importing the full session.
Workflow
- Synthesize the session progress into the following structure:
- Goal: The primary objective of the session.
- Decisions: Key architectural, design, or logical decisions made.
- Files Touched: Absolute paths of any files touched or modified.
- Risks & Open Questions: Outstanding bugs, assumptions, or open issues.
- Next Steps: Checklist of work remaining for the next session.
- Create a user-facing artifact named
handoff_draft.md under <appDataDir>/brain/<conversation-id>.
- Set
RequestFeedback: true and UserFacing: true in the ArtifactMetadata to present a "Proceed" button.
- Format the summary using a premium layout: a markdown Table for Goals/Decisions/Files, Alerts to highlight Risks, and a checklist for Next Steps.
- Notify the user to review the drafted
handoff_draft.md artifact.
- Upon the user clicking "Proceed" or giving approval, create the handoff thread (preferring MCP
thread_create or mem_fs write to prevent terminal permission prompts, falling back to CLI nmem --json t create -t "Antigravity Session - <topic>" -c "<content>" -s google-antigravity only when MCP is unavailable).
- If the user prefers a lossless transcript backup instead of a handoff summary, route to the
nmem-save-thread skill.
Always get explicit approval before creating the handoff thread. Do not auto-save handoffs silently.
