사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/minimax-ai/mcode-stack --skill handoff-doc시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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 logfor 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:
# 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.