Index of every page on this site: llms.txt
All skills
minimax-ai avatar

/handoff-doc

@0db1b4f
by MiniMaxminimax-ai/mcode-stack736 stars
50
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/minimax-ai/mcode-stack/handoff-doc

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈67 tokens for metadata: the name and description. ≈520 when used: this file.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈270 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

# 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning23d3 checks · Risk SAFE
  • Gen Agent Trust Hub23d

    The skill is a developer utility for creating hand-off documents to transfer state between chat sessions. It reads local repository information and writes summary files. The primary security consideration is the potential for indirect prompt injection via repository content.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: MEDIUM · 1 issue

Signed by skilld at 0db1b4f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 weeks ago

README badge

README badge for minimax-ai/mcode-stack/handoff-doc