メニュー
The handoff skill captures the current session in a concise file so a fresh agent can continue without replaying the conversation. Use it when pausing work, switching sessions, or pairing with `/prototype` or `/kodmap`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Ask which skill or flow fits the current situation — a router over the skills in this collection. Use when the user isn't sure where to start or which skill applies.
Reviews a change since a fixed point on two independent axes: documented repository standards and the originating ticket or spec. Use before committing or merging a ticket, when reviewing a branch or PR, or when asked to review since a base ref.
Provide a shared vocabulary and practical rules for designing deep modules, choosing seams, improving interfaces, and making code easier to test and navigate. Use when designing or restructuring a module, evaluating abstraction depth, or when another skill needs consistent architecture language.
Diagnose hard bugs and performance regressions with a disciplined evidence loop. Use when the user says "diagnose" or "debug this", or reports something broken, throwing, failing, flaky, or slow.
A relentless interview — small batches of related questions — that stress-tests a plan or design before anything gets built, leaving a paper trail of resolved terms (CONTEXT.md) and decisions (ADRs) as it goes. Use when the user wants to pressure-test an idea, sharpen a plan, or says "grill me".
Builds one well-defined ticket from its acceptance criteria through tests, review, commit, and ticket closure. Use when the user invokes `/implement` for a GitHub Issue or local markdown ticket that is ready to build.
| name | handoff |
| description | The handoff skill captures the current session in a concise file so a fresh agent can continue without replaying the conversation. Use it when pausing work, switching sessions, or pairing with `/prototype` or `/kodmap`. |
| disable-model-invocation | true |
Write a compact continuation note for the next session. Save it in the user's operating-system temporary directory, not in the current workspace.
Include:
suggested skills section naming the skills that should be considered next.Keep the note focused on continuation. Do not duplicate durable information already recorded in project artifacts. Redact credentials, secrets, and personally identifying information.
If the user supplied an argument, treat it as the next session's focus and shape the handoff around that work. For a prototype or a multi-session map, preserve the pointer that lets the next agent find the experiment or map quickly.