- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/handoff-docFrom the publisher
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.
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.If something cannot be verified, mark it "unverified".
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:
# 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.
The path of the doc and a three-line summary: goal, current state, next step.
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, o
---name: handoff-docdescription: Write a hand-off document so a fresh session or another person can continue the current task without the chat…---# stacks/ronny/skills/handoff-doc/SKILL.mdOverview
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.
FAQ
Download stacks/ronny/skills/handoff-doc/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/MiniMax-AI/mcode-stack.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.