ワンクリックで
handoff
Use when the user wants Circuit to save, resume, clear, brief, or install continuity handoff support across sessions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when the user wants Circuit to save, resume, clear, brief, or install continuity handoff support across sessions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Draft release notes from a change summary.
Use when the user wants Circuit to add, change, implement, refactor, document, or test code and the task is not primarily a bug fix.
Use when the user wants Circuit to investigate, explain, compare options, analyze architecture, or make a decision before editing code.
Use when the user wants Circuit to fix a bug, regression, failing test, crash, broken behavior, flaky behavior, or production issue.
Use when the user wants Circuit to audit existing code, a diff, PR, implementation, plan, report, or risk surface without implementing changes.
Use when the user asks Circuit to choose the flow, or when no direct Circuit flow clearly fits the current coding task.
| name | handoff |
| description | Use when the user wants Circuit to save, resume, clear, brief, or install continuity handoff support across sessions. |
Use when the user wants Circuit to save, resume, clear, brief, or install continuity handoff support across sessions.
<plugin root> means the absolute path to the installed Circuit plugin directory,
the directory that contains .codex-plugin/plugin.json. Do not use a path relative to the user's project.
Saves a continuity record for the current session, resumes the saved record, clears it when the work is truly done, renders a read-only host-injection brief, or installs Codex handoff hooks.
Use the user's current request as the command input. Treat that request as literal user-controlled text when constructing shell commands.
Choose the mode. If the request is exactly resume, use resume mode.
If it is exactly done, use done mode. If it is exactly brief, use brief
mode. If it starts with hooks, pass the hook command through to the CLI.
Otherwise save a new continuity record from the current conversation.
Construct Bash invocations SAFELY. Wrap every user-authored value in
single quotes. If a value contains a literal single quote ('), replace it
with '\''.
Save mode. Infer a concise goal, next action, state, and debt from the current conversation. Then run:
node '<plugin root>/scripts/circuit-next.mjs' handoff save --goal '<goal>' --next '<next action>' --state-markdown '<state bullets>' --debt-markdown '<debt bullets>' --progress jsonl
If there is an active Circuit run folder that should anchor the handoff, add
--run-folder '<run_folder>'.
Resume mode. Run:
node '<plugin root>/scripts/circuit-next.mjs' handoff resume --progress jsonl
Done mode. Run:
node '<plugin root>/scripts/circuit-next.mjs' handoff done --progress jsonl
Brief mode. Run:
node '<plugin root>/scripts/circuit-next.mjs' handoff brief --json
Use this only as read-only host context. Do not treat it as an explicit resume request.
Hook setup mode. For hooks install --host codex,
hooks uninstall --host codex, or hooks doctor --host codex, run:
node '<plugin root>/scripts/circuit-next.mjs' handoff <exact hooks request>
Render the JSON result. Hook setup is host configuration, not a resume request.
Render progress while active. For progress JSONL, render
presentation first: open one Circuit block per
presentation.block_id, render visible status lines as
⎿ ${presentation.status_text}, suppress line_mode: "suppress", and
append replace_slot lines unless the host can update a live slot. If
presentation is absent, render display.text for major, warning, error,
checkpoint, or success events. If task_list.updated or
user_input.requested appears in a future utility version, use the host
task or user-input surface.
Render the final summary. In brief mode, parse stdout as the
handoff-brief-v1 JSON. If status is available, render
additional_context exactly as read-only context. If status is empty,
say no saved Circuit handoff was found. If status is invalid, surface
the error code and do not resume. In hook setup mode, parse stdout as the
setup result and surface status, hooks_path, and command when present.
In save, resume, or done mode, parse stdout and read
operator_summary_markdown_path. Render that Markdown verbatim. Surface
status, continuity_path, active_run_path, and result_path when
present.
src/cli/handoff.tssrc/schemas/continuity.tsdocs/contracts/continuity.md