← ClaudeAtlas

handofflisted

Generate a structured handoff document (project identity, current state, architecture map, recent decisions, next steps/risks) so a new AI session or teammate can pick up full context fast. Use when the user types /handoff, asks to "write a handoff", "hand this off", "prep a handoff doc", or is wrapping up a session and wants context preserved for next time.
Mariano215/tack · ★ 0 · Data & Documents · score 75
Install: claude install-skill Mariano215/tack
# /handoff Turn the current repo and conversation into one markdown file a cold read can act on. Five fixed sections, no interview, best-effort from what's already knowable. Say "not assessed" rather than guess. ## Usage ``` /handoff # current project, current conversation /handoff <focus note> # e.g. /handoff emphasize the auth refactor risk ``` ## Output Write to `<scratchpad dir>/HANDOFF_<repo-name>_<UTC compact timestamp>.md`. Use the scratchpad directory path already given in your system prompt for this session; if none was given, `mktemp -d` and use that instead. Never write the file into the project repo, it's a transport artifact, not documentation. Print the full document in chat, then print the absolute file path on its own line so the user can open it or drag it into a new session. ## What to gather Don't ask the user unless a section would otherwise be entirely empty. 1. **Identity** - repo/dir name, one-line goal from README/CLAUDE.md opening lines, hard constraints from any CLAUDE.md/AGENTS.md in scope (tech stack, permanent rules, boundaries). 2. **Current state** - `git status --short`, current branch, ahead/behind main. If this session has a TaskList, sort its items into working/partial/broken/not-started; otherwise write "not tracked this session." 3. **Architecture & map** - `find . -maxdepth 2 -type d` (skip .git, node_modules, vendor, build output), key dependencies (package.json/requirements.txt/go.mod/Cargo.toml, whichev