// Writes a compact continuation handoff for another agent or future session. Use when the user asks to hand off, compact context, continue later, or preserve next steps.
| name | handoff |
| description | Writes a compact continuation handoff for another agent or future session. Use when the user asks to hand off, compact context, continue later, or preserve next steps. |
| argument-hint | What should the next session focus on? |
Use this when the useful context is in the conversation, terminal output, changed files, or linked artifacts, and the next agent needs a clean continuation point.
Write a handoff document to the temporary directory of the user's OS, not the current workspace. Resolve the temp directory with the platform temp-dir API or environment, such as $TMPDIR on macOS/Linux or %TEMP% on Windows.
Write the handoff under a project and topic folder:
<os-temp-dir>/handoff/<project>/<topic>/handoff.md
If the project or topic is unclear, infer short slugs from the current task, such as vitehub/auth-debug, skills/readme-polish, or nuxt/runtime-config.
<project> and <topic> slugs using lowercase words joined by hyphens.<os-temp-dir>/handoff/<project>/<topic>/handoff.md.<os-temp-dir>/handoff/<project>/<topic>/
+-- handoff.md
handoff.md must include project_root as an absolute path. Any project file reference in the handoff must be absolute, such as /Users/maxi/vitehub/vitehub/packages/client/src/index.ts. Never use repo-relative paths like packages/client/src/index.ts inside temporary artifacts unless they are paired with the absolute project_root.
Handoff written:
- <absolute-handoff-path>
Next:
- ...
Creates or revises one portable agent skill with concise routing, progressive disclosure, and clear safety boundaries. Use when the user wants to write, clean up, or restructure a skill.
Finds Codex session coordinates by id, title, repo path, rollout path, or topic. Use when a user or another skill needs thread metadata and rollout paths for its own review.
Reviews recent Codex sessions for repeated agent failures and skill improvements. Use for daily/weekly retrospectives, skill audits, agent-pattern analysis, or cleanup recommendations.
Clarifies fuzzy direction into durable memory and issue-shaping handoff. Use when the user wants to turn an idea, conversation, ADR, PRD, or prior session into clear agent-ready work.
Gathers internal or external evidence for one decision and returns sourced patterns. Use when design, planning, retrospectives, or architecture depends on research before deciding.
Skips obvious branches inside grilling sessions by stating the assumed answer and moving on. Use when the user says fast-forward, skip, obvious, same as me, or next unclear area.