Menü
Generate a HANDOVER.md file summarizing the current session's work. Use at the end of a session to preserve context for the next session.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Generic thinking protocol for deriving optimal solutions through iterative self-checking. Invoke BEFORE searching within the given problem space whenever the user asks for advice, judgment, evaluation, or choice. Reframes the problem, generates options, evaluates trade-offs, runs a self-answer check (does this answer the user's actual question at the right granularity, reach upstream, match expectations, offer non-obvious value?), and loops back to upstream tracing or same-level reframing if the check fails — until convergence. Applies across any domain — technical, process, organizational, decision-making, career. Triggers when the user uses evaluation or reconsideration language ("which is best", "root cause", "is this really needed", "sustainable long-term", "ほんとうに", "そもそも", "最善は", "根本は", "筋が良い"), when validating the soundness of someone's proposal from multiple perspectives, when the problem spans multiple layers (tech / process / org / regulation / UX / cost), or when clear trade-offs exist.
Review the local diff with flat-perspective sub-agents, fix findings in a loop, then create a PR via the create-pr skill once the review is clean
計画や設計について、ユーザーを徹底的に問い詰めて一緒に詰める。実装・着手の前に計画をストレステストしたいとき、または「詰めて」「グリルして」「問い詰めて」「ツッコんで」「設計レビューして」「ほんとうにこれでいい?」などのトリガー表現が出たときに必ず使う。
.claude/rules/ 配下のルールファイル (*.md) を新規作成・編集するときに、適切なメカニズム選択と paths スコープを保証する。ルールを書く前・書いた後に必ず適用する。
Orchestrate Epic issue as team leader. Delegate sub-issues to member agents in isolated worktrees. Members run in background and communicate via SendMessage.
Fetch a GitHub issue with its sub-issues, walk up to the parent Epic, list sibling issues under that Epic, fetch the body of each sibling issue, attach the implementing PR for each closed sibling with body and diff summary, gather related code, and present as a Japanese summary so the reader can grasp the whole task context including the actual contents of siblings and their PRs
| name | handover |
| description | Generate a HANDOVER.md file summarizing the current session's work. Use at the end of a session to preserve context for the next session. |
| disable-model-invocation | true |
現在のセッションの文脈を次のセッションへ引き継ぐためのハンドオーバーファイルを作成する。
現在のセッションの会話を振り返り、以下を整理する:
git status
git diff
git diff --cached
git log --oneline -10
ハンドオーバーファイルはプロジェクトルートの scratch/ 配下に保存する:
scratch/ が存在しない場合は mkdir -p scratch で作成するscratch/YYYYMMDD-HHMM-<descriptive-name>.md 形式 (例: scratch/20260511-1430-auth-refactor.md)。タイムスタンプは date +%Y%m%d-%H%M で取得し、<descriptive-name> はセッションの作業内容を反映したケバブケースの短い名前にする以下のセクション構成で書き出す:
# Handover
## What was done
- [Completed work items with brief descriptions]
## Decisions
- [Design decisions and their rationale]
## Rejected approaches
- [Approaches considered but not adopted, with reasons]
## Gotchas
- [Problems encountered and their solutions]
## Learnings
- [Key insights gained during the session]
## Next steps
- [Remaining work items, in priority order]
## Related files
- [Files that were created or modified]
生成した内容をユーザーに見せて確認してもらう。
CLAUDE.md に置くscratch/ は gitignore されるが worktree 間で共有されるため、ハンドオーバーファイルの置き場所として最適$ARGUMENTS