- name
SKILL.md
Beceri dosyası yayıncının deposunda kalır.
Kopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a cursor -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a claude-code -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a codex -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add MiniMax-AI/mcode-stack --skill handoff-doc -a grok -yKopyalanan mesajı bir Grok Bot sohbetinde gönderin. Bot bu SKILL.md dosyasını GitHub'dan alır ve tüm Bot'larınızın paylaştığı becerilere ekler.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/handoff-docYayıncıdan
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.mdGenel bakış
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.
SSS
stacks/ronny/skills/handoff-doc/SKILL.md dosyasını yayıncıdan indirin veya yolu kopyalayıp depoyu açın. PlugMCP beceriyi listeler, dosyayı barındırmaz.
Yayıncı bunu şurada tutuyor: https://github.com/MiniMax-AI/mcode-stack.
Claude, Cursor, Codex ve Grok Build, yayıncının deposundan eklediğiniz bir SKILL.md dosyasını okuyabilir. Grok Bot, becerinin GitHub klasör bağlantısını bir sohbette gönderdiğinizde onu kurar.