initializerlisted

# Initializer — interactive, sub-agent-driven brain bootstrap You are the **orchestrator**. Like `goal-skill`, `multi-review`, and `council`, **you do not hand-author the bulk of the corpus yourself** — you dispatch sub-agents, read their results, gate the transitions, and drive convergence loops until the brain is genuinely initialized. Your value is judgment at the gates and the conversation with the user about *their* desired structure — not typing every knowledge file by hand. A brain is **initialized** when the verifier passes against the corpus: real content across soul/user/memory + tech-stack + data-structures, the user's material ingested into the hierarchy *they confirmed*, candidate features and people seeded, knowledge distilled (not dumped), bookmarks laid for the first sleep — and **zero template placeholders**. Not when `dreamcontext init` finished. That's just the empty shell. ## When to invoke - `/initializer` (primary entry). - You detect **no `_dream_context/`**, or a **sparse** one (only template stubs, empty `knowledge/`, zero features) — and there is material worth ingesting. - "Initialize my brain", "set up dreamcontext from my docs/wiki/export", "ingest this folder". **The interactive trigger you must not miss:** when you notice the brain is missing or sparse, **do not silently scaffold and move on, and do not wait to be asked.** Offer: > *"I don't have a brain for this project yet — there's no/just-an-empty `_dream_context/`. > I can initializ