Skip to main content
skill CX Codex

handoff-doc — Claude Code skill: what it does, how to install

handoff-doc is a Claude Code skill that writes a structured handover file before a session reset or task switch. It preserves critical context without relying on full chat history.

MIT ★ 741 updated 2026-11-11

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add MiniMax-AI/mcode-stack
/plugin install ronny@mcode-stack
Open on GitHub

What handoff-doc does

The skill inspects project state instead of conversational memory. It runs git status, checks branch logs, inspects diffs, and notes actual test outcomes. Any claim that cannot be validated via project files or tool output is marked as unverified.

The output document is saved directly into the repository, such as docs/handoff/<task>.md. Its template captures the end goal, binding architectural constraints, rejected approaches, current test verification, and immediate next steps. The agent asks for confirmation before committing the file.

Execution wraps up with the relative path to the new file and a three-line summary covering the goal, verified progress, and the exact next action.

What it helps with

  • preserve task context before wiping an agent session window
  • hand off an unfinished branch to a colleague or a fresh agent session
  • record abandoned technical decisions and reasons to avoid repeated work
  • verify real progress using git status and test commands instead of chat assumptions

Example prompts for the agent

  • Write a handoff doc for this task before I clear the session
  • Create a handoff brief in docs/handoff for the current feature branch
  • Summarize progress, rejected options, and next steps into a handoff file

How to install handoff-doc

1Plugin marketplace

/plugin marketplace add MiniMax-AI/mcode-stack
/plugin install ronny@mcode-stack

This installs the whole ronny plugin with all its skills

2Skills CLI (Vercel)

npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a claude-code

3Manually: put the files in place

~/.claude/skills/handoff-doc/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/handoff-doc/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about handoff-doc

How to install handoff-doc in Claude Code?

Run /plugin marketplace add MiniMax-AI/mcode-stack, followed by /plugin install ronny@mcode-stack. Alternatively, execute npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a claude-code.

What does handoff-doc do?

It creates a concise handover Markdown file based on git status, diffs, and test runs so a fresh session can pick up where the previous one stopped.

What is required to run handoff-doc?

It only requires access to the local git repository and test commands; no external APIs or paid accounts are needed.

Source text

SKILL.md · MIT
---
name: handoff-doc
description: Write a hand-off document so a fresh session or another person can continue the current task without the chat history. Use when switching tasks, after several compactions, before clearing a session, or when asked to write a handoff, brief, or progress doc.
---

# Hand-off Doc

Important state should not live only in the context window. A short, readable
hand-off doc lets you clear the session, start a new one, or pass the work to
someone else, and continue with exactly what you consider important.

Companion to MCode Engineering Notes 01 and 03.

## 1. Gather from real sources

Before writing, check the actual state instead of relying on memory of the
conversation:

- `git status`, `git log` for the branch, and the current diff.
- The test or build commands that were run and their latest real results.
- Any existing design, progress or todo files in the repository.
- Open issues, PRs or review comments linked to the task.

If something cannot be verified, mark it "unverified".

## 2. Write the doc

Save it in the repository (for example `docs/handoff/<task>.md`) or wherever
the project keeps working notes. Ask before committing it. Use this template:

```markdown
# Hand-off: <task>

Updated: <date>   Branch: <branch>   Last commit: <short sha>

## Goal
One or two sentences. What "done" looks like, and the acceptance criteria.

## Decisions made
- <decision> - because <reason>

## Constraints to keep
- <constraint the next session must not break, e.g. "do not change the public API">

## Ruled out
- <approach> - why it was dropped (so nobody tries it again)

## Current state
- Done: ...
- In progress: ...
- Verified by: <command> -> <result>

## Next steps
1. <the very next concrete action>
2. ...

## Watch out for
- Known pitfalls, flaky tests, environment quirks.

## Pointers
- Key files, functions, issues, PRs.
```

Keep it short. It is a brief, not a transcript. Leave out debugging
narratives and tool output that can be reproduced.

## 3. Hand over

- Tell the user where the doc is.
- In the new session, reference the doc first (for example by mentioning its
  path) and ask the agent to restate the goal and the next step before it
  starts.
- Update the same doc at each milestone instead of creating new ones.

## Output

The path of the doc and a three-line summary: goal, current state, next step.

© Ronny (MiniMax Code team) · MIT · MiniMax-AI/mcode-stack

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set27

The whole set →
youfang youfang is a Claude Code plugin that converts architecture diagrams into Keynote-style Magic Move slide decks. Builds a single offline HTML file where shared elements morph between views. CX Codex ★ 741repo stars req-tpm req-tpm is a Claude Code plugin that tracks requirements from intake through outcome review. Its skills capture a measurable goal, record design decisions, and follow progress. CX Codex ★ 741repo stars jiachen jiachen is a Claude Code plugin for evidence-based PR checks with MCode Review. It reviews branches on request or runs in GitHub and GitLab CI, where a script determines the verdict. CX Codex ★ 741repo stars ronny ronny is a Claude Code plugin with skills for code review, agent workflows, and checking agent output. It comes into play for reviewing changes, delegating work, and auditing how agents operate. CX Codex ★ 741repo stars review-capacity-check review-capacity-check is a Claude Code skill that checks unfinished agent work before another launch. It runs before parallel batches and during weekly reviews. CX Codex +1 ★ 741repo stars taste-to-checks taste-to-checks is a Claude Code skill that turns repeated review fixes into tests, lint rules, hooks, CI steps, or project rules. It activates after the same miss returns. CX Codex +1 ★ 741repo stars trajectory-review trajectory-review is a Claude Code skill that examines an agent’s path to a result. It runs after a task or eval finishes, fails, or changes outcome. CX Codex +1 ★ 741repo stars harness-experiment Harness-experiment is a Claude Code skill that runs controlled experiments to validate agent scaffolding changes. It triggers when adjusting prompts, tools, or subagent layouts for performance tracking. CX Codex +1 ★ 741repo stars

Project sponsors

Companies that keep this analytics open