onboarding

name	onboarding
description	First-time setup for a fresh MUM instance. Use when the knowledge/ folder has no core content yet, or when the user asks to (re)onboard. Interviews the user and writes the initial core knowledge files. Do not use for ongoing knowledge updates during normal work — that's the self-evolve protocol.

Onboarding

You set up a brand-new MUM instance by interviewing the user and writing the first core knowledge files into knowledge/. Keep it light — capture the essentials, not their whole life. MUM fills in the rest over time via self-evolution.

How to run it

Interview the user one question at a time — ask, wait for the answer, then ask the next. Keep questions short. Skip anything they'd rather not share. Aim to fill these two core areas:

1. Who you are & how you work → knowledge/user.md Name, what they do, how they work, and recurring context that helps MUM be useful. (Repeatable procedures become skills, not notes here.)
2. How MUM should behave → knowledge/mum.md Tone, level of detail, defaults, dos and don'ts, how they like an assistant to work.

If something they share clearly belongs to a life/work domain (not core context), create a domain note for it following the knowledge skill's convention.

Steps

1. Confirm the repo is private before collecting any personal details. If it's public or you can't tell, stop and ask the user to make it private (or confirm) before continuing.
2. Briefly explain what onboarding will do, then start the interview.
3. As answers come in, write concise notes into the files above. One topic per file, facts over prose. Create domain subfolders only if the conversation clearly calls for one.
4. When both core areas are covered, summarize what you captured and confirm.
5. Replace the README. This is a fresh instance, so README.md is still the template's one. Rewrite it README.md with a short, private, personal note to the owner — what this repo is and how to use it.
6. Commit the new knowledge/ files and the rewritten README.md to main.

Gotchas

• Re-onboarding: if knowledge/ already has core content, confirm before overwriting — update files in place rather than clobbering them.
• Don't over-interview or pre-create empty domain folders; capture the essentials and let self-evolve fill the gaps as they come up.

Rules

• Keep it lean — capture what's actually useful, don't pad files.
• After onboarding, follow the self-evolution protocol to keep knowledge current.