levelup

# MasterMind — Level Up MasterMind improves by **editing its own knowledge base** (its weights are fixed). This skill is the disciplined loop that does it. Read `~/.mastermind/engineering/active-field.md` first to know the active field and its pack path (`engineering/fields/<field>/`). ## Pick exactly one mode Take the mode from the argument; default to **capture**. **Do one mode per run** — they touch different files under different rules, and blending them is how a lesson lands in the wrong file. | Mode | Trigger | Read | | --- | --- | --- | | **`capture`** (default) | a correction, review finding, or bug worth remembering | below — it's the whole job | | **`refresh`** | standards may have drifted from the live ecosystem | `refresh.md` **before writing anything** — it carries the upstream-only write allowlist | | **`bootstrap <field>`** | a new domain or stack with no pack | `bootstrap.md` | Adding or rewriting a **skill or agent** is not a mode — it's a separate discipline: read `authoring.md`. ## `capture` (default) — harvest lessons from this session/recent work 1. Scan the recent work for durable, generalizable lessons: user corrections ("no, do X"), real `code-reviewer` findings, bugs fixed, and choices that proved right. Ignore one-off/project-specific noise — only keep what will apply to *future* tasks. 2. For each: append a one-line rule + bracketed "why" to `~/.mastermind/engineering/fields/<field>/lessons.md`. Deduplicate against existing lessons. ...