ワンクリックで
handoff
Use when an active frontend, backend, or integration workstream must pause and record a sidecar HANDOFF.md.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when an active frontend, backend, or integration workstream must pause and record a sidecar HANDOFF.md.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | handoff |
| description | Use when an active frontend, backend, or integration workstream must pause and record a sidecar HANDOFF.md. |
Pause a whole workstream without transferring or resetting its current TDD task.
TRACK.md, current TASK.md, contract,
and any prior handoff. Reject a non-ACTIVE track.HANDOFF.md using the packaged template.TRACK.md status to PAUSED and retain current_task unchanged.Do not create a token, move a task between tracks, create a worktree, or change task lifecycle solely because the workstream is paused.
Use when a paused frontend, backend, or integration workstream must resume from its sidecar TRACK.md and HANDOFF.md records.
Use when the user explicitly requests a complete Electron workflow rather than a small edit or one-stage request.
Use when the current host has dated WRITE_SUBAGENT: VERIFIED evidence and the user requests parent-supervised native-subagent TDD for one workstream task.
Use when a declared frontend, backend, or integration workstream has one READY task for parent-led sequential TDD.
Use when an approved Electron contract must split one feature into frontend, backend, and integration workstreams with TDD task records.
Use when an Electron failure or confirmed review finding can be reproduced and needs root-cause analysis, a minimal fix, and regression verification. Do not use for speculative cleanup, broad refactoring, initial review, or masking failures by weakening safeguards.