Menu
Use when work needs to survive losing context โ before a /clear on a long task, when pausing something unfinished, when handing over to a teammate or the next session, or when the context window is filling up on multi-day work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use on the first substantive work in a project MasterMind isn't set up for yet, when the user says "init", "initialize", "set up MasterMind", "onboard", "get me ready", or when no field pack matches the project's detected stack.
Use after a correction or review finding worth remembering, when standards may have drifted from the live ecosystem, when switching MasterMind to a new domain or stack, or when the user says "remember this", "learn from that", "level up", "update your knowledge".
Use when implementing any non-trivial feature, change, or fix โ "build me X", "add this feature", "implement this", "make this work", "can you create". Covers new functionality, meaningful changes to existing code, and anything where quality matters. Not for a one-line diff โ just do that.
Use when a bug isn't obvious, resists a quick fix, keeps coming back, or you're about to start guessing โ "why is this broken", "this keeps happening", intermittent or flaky failures, a crash you can't explain, behaviour that makes no sense. Not for a typo or an obvious mistake.
Use when an internal package, module, or shared component has little or no usage documentation and people (or future AI sessions) keep using it wrong โ "document this", "write docs for our library", onboarding someone onto an internal API, or handing a package to another team.
Use when the user asks what MasterMind can do or how to drive it โ "help", "what can you do", "how do I use this", "what commands are there", "list your skills", "what are my options" โ or when they seem unsure how to get started.
| name | handoff |
| description | Use when work needs to survive losing context โ before a /clear on a long task, when pausing something unfinished, when handing over to a teammate or the next session, or when the context window is filling up on multi-day work. |
Context is the fundamental constraint (~/.mastermind/engineering/core/agent-loop.md); a long task shouldn't lose its thread to a
reset. Capture just enough to resume cold โ high signal, low tokens.
Summarize, don't dump โ link or point to detail rather than pasting it. Write it where the next session
will look (HANDOFF.md, a scratch file, or the issue). Prune it when the work completes.
A tight HANDOFF.md: goal, state checklist, decisions, file map, gotchas, resume+verify steps.
