Menu
Compact the current conversation into a handoff document for another agent or session to pick up.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Find deepening opportunities in the codebase — refactors that reduce coupling, simplify interfaces, and improve AI-navigability. Use when improving architecture, finding refactoring opportunities, or making a codebase easier to work with.
Use before any feature work — explores intent, asks clarifying questions one at a time, produces a design doc. Invoke before writing any code or plan.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "less tokens", or invokes /caveman.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → review. Use when something is broken, throwing errors, or regressing.
Interview the user or a design relentlessly until reaching shared understanding. Walk down every branch of the decision tree, resolving dependencies one by one. Use when stress-testing a plan, clarifying design, or the user says "grill me".
Use at the start of any session to understand which skill to invoke. Maps the full workflow — feature development, bug fixing, architecture, and utilities — for a C++ game server project with SVN.
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent or session to pick up. |
| argument-hint | What will the next session focus on? |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to a path produced by mktemp -t handoff-XXXXXX.md (read the file before writing to it).
Suggest which skills the next session should use.
Do not duplicate content already captured in other artifacts (PRDs, plans, SVN commit messages, diffs). Reference them by path instead.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
# Handoff — [Date] [Focus]
## Context
[What we were working on and why]
## Current State
[What is done, what is in progress, what is blocked]
## Key Files
[Exact paths to plans, PRDs, or design docs relevant to the next session]
## Next Steps
[Ordered list of what to do next]
## Suggested Skills
[Which skills to invoke in the next session, in order]
## Open Questions
[Anything unresolved that the next session needs to decide]