<< All versions

Skill v1.0.0

currentLLM-judged scan90/100
asarchami/dotfiles/handoff
──Details
PublishedOctober 21, 2026 at 08:27 PM
Content Hashsha256:c9b44f861aeb1d45...
Git SHAadb714d70b9b
──Files
Files (1 file, 3.0 KB)
SKILL.md3.0 KBactive
SKILL.md · 64 lines · 3.0 KB

version: "1.0.0" name: handoff description: "Write a handoff document that compacts this session so a fresh agent can continue the work." license: MIT


Handoff

Leading word: handoff. A relay race is won at the baton pass, not the sprint. Handoff means the next agent picks up the work without re-reading this conversation: current state, decisions, next actions, and pointers to the artifacts that already hold the detail.

Steps

  1. Assemble the context. Collect the working state: what was built or decided, open threads, pending questions, and every artifact that already captures this work (specs, PRDs, plans, ADRs, issues, commits, diffs).

Done when: each artifact relevant to the work is listed with a path or URL.

  1. Write the compact. Summarize the current state, key decisions, and the next actions — one screen, readable in minutes. Reference artifacts by path or URL; never restate their content.

Done when: nothing in the document duplicates an artifact's content, and the next agent can start without reading the conversation.

  1. Name the suggested skills. Add a Suggested skills section listing the skills the next agent should invoke. Confirm each name is a real, loadable skill in this environment before suggesting it.

Done when: every suggested skill appears in your available skills.

  1. Redact. Scan the draft for API keys, passwords, tokens, and personally identifiable information.

Done when: no sensitive value survives in the document.

  1. Save to the temp directory. Write <project>-handoff-<YYYY-MM-DD>.md to the OS temp directory ($TMPDIR on Unix/macOS, %TEMP% on Windows), not the workspace.

Done when: the file exists outside the workspace and its absolute path is reported to the user.

  1. Tailor to the next session. If the user's invocation describes what the next session will focus on, shape the next actions and suggested skills around that focus.

Done when: the document's next actions match the stated focus.

Reference

Suggested document shape

SectionPurpose
Current stateWhat exists and works now
DecisionsChoices made and why
Next actionsOrdered steps for the next session
Open questionsThings blocking or undecided
Suggested skillsSkills the next agent should invoke
ArtifactsPaths/URLs to specs, PRDs, ADRs, issues, commits, diffs

Temp directory

The OS temp directory — os.TempDir() — $TMPDIR on Unix/macOS, %TEMP% on Windows. A handoff document never belongs in the workspace; it is transient by design.

Watch for

MistakeFix
Restating spec/ADR contentReference it by path or URL
Saving into the workspaceWrite to the OS temp directory
Leaving secrets or PII in the documentRedact before saving
Suggesting a skill that doesn't existVerify against available skills
Producing a full transcriptCompact — a fresh agent reads it in minutes
All versions