From seiraiyu-skills
Compact the current conversation into a self-contained handoff document so a fresh agent (or a future you) can resume the work without re-reading the whole session. Use when the user says "hand off", "write a handoff", "summarize this session for another agent", "I'm running low on context", "pause and pick up later", or before clearing/compacting a long conversation. If the user passes arguments, treat them as the focus of the next session and tailor the doc to it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/seiraiyu-skills:handoff What will the next session focus on? (optional)What will the next session focus on? (optional)This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn the live conversation into a **handoff document**: everything the next agent
Turn the live conversation into a handoff document: everything the next agent needs to continue, and nothing it can find for itself. Optimize for a cold start — assume the reader has zero memory of this session.
This is complete when:
/clear then paste) naming the doc's absolute pathIf the user passed arguments, that is the next session's mission — lead with it and bias every section toward it (the relevant files, the open question, the next action).
If they didn't, infer the most likely continuation from the recent turns and state your assumption in one line at the top so the reader can correct it.
Write to the OS temp directory, not the current workspace (the next agent may be in a different repo, branch, or worktree). Resolve it in this order:
# Cross-platform temp dir + collision-proof, descriptive filename
DIR="${TMPDIR:-${TEMP:-/tmp}}"
STAMP="$(date +%Y%m%d-%H%M%S)"
FILE="$DIR/handoff-<slug>-$STAMP.md" # <slug> = 2-4 word kebab-case topic
$TMPDIR then /tmp.%TEMP% / $env:TEMP.handoff-auth-rate-limit-20260608-141030.md) so the
user can find it later among other temp files.Use the template in references/handoff-template.md. Fill every section; delete a heading only if it is genuinely empty.
Guiding rules:
| Do | Don't |
|---|---|
Reference artifacts by path/URL (See plan.md, PR #214, git show abc123) | Paste diffs, full files, or long logs |
| Capture decisions and their rationale ("chose X over Y because Z") | Re-narrate the play-by-play of the chat |
State the exact next action ("run npm test auth, expect 2 failures in …") | Leave the next step vague ("continue the work") |
| List blockers, dead ends, and things already tried | Make the next agent rediscover dead ends |
| Record exact commands, file paths, env/flags needed to resume | Assume the reader shares this session's working dir |
| Note current git branch, dirty state, unpushed commits | Omit where the code actually lives |
Keep it scannable — headers, bullets, tables. A handoff nobody reads is worthless.
Before saving, scrub:
.env values → [REDACTED]When in doubt, redact the value but keep the name so the reader knows a secret is needed there (e.g. DATABASE_URL=[REDACTED — in 1Password/Neon]).
Always include a Suggested skills section listing skills the next agent should invoke, each with a one-line why and (if known) the trigger phrase. Draw from the skills available in the target environment. Common picks:
respond-to-coderabbitai — if a PR is open and awaiting review resolutionjira — if work is tracked in Jira and the ticket needs updating/transitioningneon — if the work touches a Neon database branchsop-creator — if the outcome should be documented as a runbookverify / code-review — before claiming the resumed work is doneOnly suggest skills that plausibly apply — an irrelevant list erodes trust.
The whole point is to start fresh. After writing the doc, present a paste-ready
prompt the user can run in a clean context — mirroring how /plan ends. Use the
actual file path; the user copies one block after clearing.
Handoff written: /tmp/handoff-auth-rate-limit-20260608-141030.md
Covers: rate-limit middleware half-built on branch `feat/rate-limit`; next step is
wiring the Redis store (TODO at src/middleware/rateLimit.ts:42). PR #214 open.
To continue with a clean context, run `/clear` then paste:
Read the handoff at /tmp/handoff-auth-rate-limit-20260608-141030.md and resume the
work. Start with the "single most important next action", and invoke any skills
listed under "Suggested skills".
Keep the pasted block self-contained: it must name the absolute path and tell the fresh agent to start from the doc — that agent has no memory of this session.
npx claudepluginhub stonelyd/seiraiyu-skills --plugin seiraiyu-skillsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.