- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill handover -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill handover -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill handover -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add phuryn/product-engineering --skill handover -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/phuryn/product-engineering/tree/HEAD/agent-harness/skills/handoverDel publicador
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.mdResumen general
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.
Preguntas frecuentes
Descarga agent-harness/skills/handover/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/phuryn/product-engineering.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.