handoff
Skill1 starsChanged 2 months agoMITView on GitHub
別セッションで再開するために区切るとき、「引き継ぎを作って」「handoffして」と言われたときに必ず使う。
191 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- element-hq/element-calltheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- niki914/zafirotheir own version, first seen Nov 15, 2026
- davidondrej/skillstheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use decision-mapping, setup-ts-deep-modules and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 47 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 59 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 105 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 101 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 62 projects that use this
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 325ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adrSkill
- architecture-checkSkill
- brainstormSkill
- branch-namingSkill
- codex-delegateSkill
- config-explainSkill
- config-setSkill
- cross-reviewSkill
- design-interviewSkill
- diagnosing-bugsSkill
- fix-ciSkill
- leakage-checkSkill
- literature-reviewSkill
- mlflow-logSkill
- multi-seedSkill
- mutation-testSkill
- paper-writingSkill
- pre-mortemSkill
- property-testSkill
- python-standardsSkill
- refactor-scoutSkill
- regression-suiteSkill
- retrospectiveSkill
- security-reviewSkill
- spec-checklistSkill
- tddSkill
The file
Files
ハンドオフ文書の作成
長い会話やまたぐ作業を、次のセッションが最小限の文脈で再開できるよう コンパクトにまとめる。
含める内容
- 今何に取り組んでいたか(1-2文)
- これまでに固まった決定事項(ADRがあれば参照するだけでよい)
- 現在の状態(どこまで終わっていて、何が残っているか)
- 次にやるべき具体的なステップ
- 関連ファイルのパス(計画ファイル、設計書、変更したコードなど)
- 未解決の疑問点・保留事項
実行状態スナップショット
.claude/state/<slug>.json(存在する場合)の内容をそのまま埋め込むこと(必須)。
散文の要約だけでなく、state_gate がスキーマ検証済みの構造化状態も残す。
- 埋め込み方: 該当ファイルの中身をコードブロックでそのまま貼る
- 別マシンでの復元: 受け取った側は同じ内容を
.claude/state/<slug>.jsonに 書き戻してから作業を再開する(state_gate が書き戻し時にスキーマを検証する)
含めないこと
- 会話の逐語的な再現(要約に徹する)
- 既にコードやドキュメントに書かれている内容の重複(パスを示すだけでよい)
公開・共有前チェックリスト
公開・共有(handoffの保存、論文原稿の提出、リポジトリの公開など)の前に、 以下を確認する。
- git 履歴に秘密情報・生データが含まれていないか
- notebook 出力に生データや個人情報が残っていないか
- テスト fixture に実データが紛れていないか
- ログに秘密情報・生データが含まれていないか
- レポート・evidence に集計値以外の生データが含まれていないか
- MLflow の記録に生データ・秘密情報が含まれていないか
- exports 予定物が持ち出し規制(集計値・図・ハッシュのみ)を満たしているか
保存先
.claude/handoffs/YYYYMMDD-<topic>.md に保存する
(.claude/handoffs/ が無ければ作成する)。
次のセッションでの使い方
新しいセッションで「.claude/handoffs/xxx.md を読んで続きから再開して」と 伝えると、そこから作業を再開できる。Windows/Linux間などマシンをまたぐ 場合は、リポジトリを git pull すればハンドオフ文書ごと引き継がれる。
自動記録との違い
セッション上限からの自動再開(record_session_state.py が毎ターン上書きする
.claude/checkpoints/session_state.md、gitignore対象、同一ブランチ・同一
マシンのみ)は何もしなくてよい。別マシン・別クローンへの引き継ぎや要約整理には本スキルを使う。
.claude/state/<slug>.json も同様に gitignore 対象でマシンをまたがないため、
別マシンへ引き継ぐ場合は上記「実行状態スナップショット」節での埋め込みが必要になる。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

