- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill handover -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill handover -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill handover -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add phuryn/product-engineering --skill handover -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/phuryn/product-engineering/tree/HEAD/agent-harness/skills/handover게시자 제공
Write the one note the next session reads first. The session is ending, or its context is; work continues tomorrow, in a fresh session, or with another agent. Start that session from what is true rather than what this session remembers.
/agent-harness:handover Claude Code, plugin installed
/agent-harness:handover the next session finishes the billing stage
$agent-harness:handover Codex, plugin installed
/handover · $handover the skill folder copied into a repository
Check what this session believes against reality before writing a word.
git status, the branch, commits made this session, and files the work touched.An inherited report is a claim, this session's own memory included.
Keep it short enough to stay true, preserving the evidence. Evidence costs most to lose. A re-run experiment costs money; restating a number from memory is how a wrong one reaches the owner.
Use the project's own handover convention before creating a new file. Use its status board, plan's status lines or existing handoff file. With none, keep one HANDOVER.md at the repository root, rewritten in place each time. It says what is true now, not the history.
Use the flight-deck skill for hours, multiple sessions or background jobs. That work wants its status board and log instead of a single note. A few lines are enough for a short session.
Name where secrets are kept without putting them in the handover. No keys, tokens, passwords or connection strings.
End with the next session's starting line and anything left running. For example: Read HANDOVER.md and start from its next action.
Each rule's origin, the case that taught it, is in receipts.md beside this file; read it when a rule's edge is unclear.
A fresh session given only the note can say what the work is for, what is verified and what is not, and run the next action without asking what happened.
Write the handover a fresh session starts from: the objective, what is true now, the evidence actually obtained, what is left, the open decisions and the next concrete action, reconciled with the disk
---name: handoverdescription: Write the handover a fresh session starts from: the objective, what is true now, the evidence actually…---# agent-harness/skills/handover/SKILL.md개요
Write the handover a fresh session starts from: the objective, what is true now, the evidence actually obtained, what is left, the open decisions and the next concrete action, reconciled with the disk first. Started by name only: /agent-harness:handover in Claude Code, $agent-harness:handover in Codex.
FAQ
게시자에게서 agent-harness/skills/handover/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/phuryn/product-engineering에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.