handoff
Skill4 starsChanged 22 days agoMITView on GitHub
Cierra una tarea dejando el relevo escrito en el repo, para que otra sesión, otro equipo u otro agente continúe sin releer el historial. Usar cuando el usuario pida cerrar, pausar o dejar handoff, y al terminar una tarea antes del commit final.
- Reads credentials
191 other projects use a version of this.
Adopted by
Most recently taken up by
- xiaoxiaosrm/dsh-mattpocock-skillstheir own version, first seen Nov 8, 2026
- ethosagent/ethostheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- glebis/claude-skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use decision-mapping, setup-ts-deep-modules and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 42 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 93 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 87 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 51 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 54 projects that use this
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- withcoral/coral★ 4.9ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- core/AGENTS.mdAGENTS.md
- skills/sdd-init/templates/AGENTS.mdAGENTS.md
- skills/sdd-init/templates/CLAUDE.mdCLAUDE.md
- nombre-de-la-skillSkill
- sdd-changeSkill
- sdd-implementSkill
- sdd-initSkill
- sdd-planSkill
- sdd-specSkill
- sdd-validateSkill
The file
Files
El relevo viaja por Git con el código, en el mismo commit. Nada lo escribe solo: se hace al cerrar la tarea.
Dos ficheros
HANDOFF.md (raíz del repo, o docs/HANDOFF.md si ya vive ahí). Se reescribe entero en cada cierre: es el estado, no un historial.
# Handoff — <proyecto>
fecha: AAAA-MM-DD · agente: <herramienta y modelo> · rama: <rama> · commit: <hash corto>
## Estado actual hecho y verificado (con la evidencia) / a medias / propuesto sin ejecutar
## Decisiones tomadas qué se decidió y por qué, incluidas las alternativas descartadas
## Archivos tocados
## Para arrancar en otro equipo qué no viaja por Git y cómo se reconstruye (.env desde .env.example, datos, modelos, servicios)
## Bloqueos o riesgos
## Siguiente paso uno, ejecutable hoydocs/ERRORES.md. Solo se añade, nunca se reescribe. Una entrada por error real del desarrollo que costó tiempo:
## AAAA-MM-DD · <síntoma en una línea>
- Dónde: fichero, comando o servicio
- Causa: la real, no la primera sospecha
- Intentos que no funcionaron: para que nadie los repita
- Solución: qué se hizo, con el commit
- Cómo evitarlo: la comprobación o regla que lo habría paradoReglas
- Concreto: "se cambió X en Y para resolver Z", no "varios cambios".
- Distingue lo verificado de lo propuesto. Si no se comprobó, se dice.
- Un bloqueo dice qué está parado, por qué y qué hace falta para desbloquearlo.
- Sin secretos ni tokens: nombres de variables, nunca valores. Rutas relativas al repo.
- Si un documento que hace falta para continuar está en
.gitignore, se avisa al usuario en el cierre: o viaja, o se anota en "Para arrancar en otro equipo". - El cierre va en el mismo commit que el trabajo. El push sigue la regla 10 de
AGENTS.md; amaino a producción, solo con el sí del usuario.
Quien retoma lee HANDOFF.md y docs/ERRORES.md, y comprueba el estado real antes de fiarse.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

