메뉴
Prepare, receive, or recover a same-machine central-agent custody handoff while preserving the complete plan and acceptance boundary. Use only when the owner requests a central session/model/harness transfer or recovery.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/vibevm/vibevm --skill steward-handoff명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | steward-handoff |
| description | Prepare, receive, or recover a same-machine central-agent custody handoff while preserving the complete plan and acceptance boundary. Use only when the owner requests a central session/model/harness transfer or recovery. |
@fact:HANDOFF-CENTRAL-ONLY This skill transfers owner-facing central custody, not work to a subagent. It never delegates acceptance. @status:impl/done
@fact:HANDOFF-PREPARE-PROCEDURE Follow
spec://org.vibevm.world/multi-user-planning/flows/multi-user-planning/custody-and-handoff#offer:
verify the tree; backscan mandate/plan/evidence/artifacts; write the immutable
offer and comprehensive HANDOFF.md; hash both handoff and plan; set custody
to offering; then become repository- and plan-read-only. A summary without
that fence is not a handoff. @status:impl/done
@fact:HANDOFF-RECEIVE-PROCEDURE Read all authorities and the complete bundle,
verify hashes and repository state independently, enumerate discrepancies,
write accepted, accepted-with-exceptions, or rejected receipt, and advance
custody only for an accepted receipt. Preserve all dirty/worker work as
candidate. Report restored state and wait for the owner before execution.
@status:impl/done
@fact:HANDOFF-RECOVER-PROCEDURE Preserve artifacts, verify holder unavailability, write a takeover record with the owner's authorization and observed accepted boundary, advance epoch, and treat everything after durable project acceptance as candidate. Never delete first or use staleness alone as authority. @status:impl/done