session-handoff
Use when work must continue in another model, runtime or computer without restarting.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when work must continue in another model, runtime or computer without restarting.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks to "подготовить weekly launch update", "сделать еженедельное обновление по запуску", "написать update для CEO", "собрать статус запуска", "выделить риски запуска", "подготовить статус по проекту", or "prepare a weekly launch update". It creates concise launch status updates from project context, weekly changes, risks, blockers, and decisions needed from leadership.
Use when a working process must be continued by another person or agent from an exact state.
Use before publishing or accepting an agent output as complete.
Use when a user describes a repeatable process and needs a process contract with trigger, inputs, output, owner, definition of done, source map and first-run contract. Triggers include “собери бриф процесса”, “operating brief”, “опиши процесс”, and “спецификация процесса”.
Use when an operating brief or process description exists and the user needs to identify the first automation candidate, assign agent/automation/person roles, map human gates, and place each step on the adoption curve. Triggers include “разбери процесс”, “process audit”, “что автоматизировать”, and “приоритизируй шаги”.
| name | session-handoff |
| description | Use when work must continue in another model, runtime or computer without restarting. |
Done when the next model can verify state before changing files.