init

# Initialize — get MasterMind ready for this project, fast The goal: a new user goes from "installed" to "the brain is set up for my stack and knows what I'm building" in a **few quick steps** — never an interrogation. Detect what you can; ask only what you can't. Run **once per project**; if this project already built its field, you're set — skip this. **Nothing ships pre-baked.** A fresh install carries only the engine and `engineering/fields/_template/` — no field, because a pack tuned to someone else's stack is worse than none (dead weight that misleads). So init's core job is to **build this project's field from the template**, tuned to the real stack. This is where the measured quality lift comes from; without it you still apply solid general judgment, but the domain pack is the difference. ## Keep it short (the #1 rule) **Detect before asking; never ask what you can read, and never hand the user a menu of technical options.** A developed project needs **zero questions** — continue with its own stack. A greenfield project needs **one open question** ("what do you want to build?"), answered in their own words. The whole thing should feel like 20 seconds, then you're working. ## Path A — the project already has code 1. **Detect the stack** — `package.json`/lockfile, configs, framework + versions, DB, test runner, folder shape (`core/agent-loop.md`). This is free; never ask what you can read. 2. **Set up its field:** - **This project already built a field that fi...