onboardlisted

> Inherits `references/kernel.md` (the provenance contract). Reads `references/wiki-spec.md` for schema. Note on provenance scope: onboarding writes `context/` and `digests/`, which hold YOUR direct testimony about yourself and your business — not `wiki/` canon — so they don't need `src` blocks. The cite-or-refuse gate kicks in the moment any of these facts get promoted into `wiki/` (via `/capture`). Until then, `context/` is "you telling the brain who you are," kept separate from the sourced wiki. ## What this skill does A single combined wizard. It reads or writes `intake.md` (the canonical 7-question intake), conducts the interview if the file isn't filled, then scaffolds the Day-1 file set inline at the end of the run. There is no separate scaffold skill — this is one flow. **The wow moment:** at the end, suggest the closing prompt *"Try this — ask me: what should I focus on this week?"* The user runs it once. That's the wow. The prompt itself plants the leverage instinct — asking, of any task, *to what extent could this be automated?* — for them to internalize. ## When NOT to run this - Already onboarded and just refreshing → still run, but skip questions already answered (idempotent). - Wiring up a new connection → that's not onboarding. Point them at `connections.md` to edit directly. ## Execution ### Step 1 — Read the intake Read `intake.md`. Check which Q1-Q7 sections have content vs. `[Your answer here]` placeholders. - **All filled** → skip Step 2, jump t