handoff — transfer session context through a GitHub issue, not a local file

运行环境入口约定：本仓库的 .claude/skills 以 Claude Code 为源，示例默认写 /tunan:*。若同一 skill 在 Codex 中运行，所有面向 sponsor 的可复制入口在输出前改写为 $tunan:*；Claude Code 中保持 /tunan:*。

This skill does what /handoff:create and /handoff:resume do — capture the state of an in-progress task so any agent can continue it later — but the handoff lives in a GitHub issue labeled tunan:handoff, never in a local HANDOFF.md. This keeps handoffs in the same issue-state store as every other tunan artifact (requirements, plans, solutions, retros), so they work across machines and sessions and never touch the working tree.

handoff is its own artifact kind, distinguished by the tunan:handoff label — like tunan:idea / tunan:retro. It is not a feature-pipeline stage; for resuming an interrupted lfg feature at the right phase, use the resume skill instead (it reads a feature issue's labels and marker comments). This skill is the lighter, free-form session-to-session context transfer.

Invocation