initlisted

# /orient:init Scaffold a small, context-cheap documentation system into this repo, or repair an existing one. This writes files, so it is user-invoked only and every write is a proposal the user approves — never a silent write. Show the drafted content before writing it. Work through these steps in order. ## 1. Resolve the docs directory Read `CLAUDE_PLUGIN_OPTION_DOCS_DIR` from the environment. If unset or empty, use `docs`. Call this `$DOCS_DIR` for the rest of the run. Every path below is relative to the repo root. The one artifact every future session depends on is the CLAUDE.md pointer block (step 6) — it carries the triggers that make decision-capture work. If there's any chance you won't finish every step, write that block first; the rest of this flow only refines the docs it points to. ## 2. Detect an existing setup (repair mode) If `$DOCS_DIR/STATE.md` or `$DOCS_DIR/decisions/` already exists, switch to repair mode: report what exists, propose only additions, and never overwrite an existing file. `init` must be safe to run repeatedly. ## 3. Survey the repo with a subagent Say one line first so the wait is expected, not a suspected hang: `Surveying the repo (runs in a subagent, ~30-60s on large repos)...` Then dispatch the `repo-cartographer` agent. Do not read the repo yourself — the point is that the survey burns the subagent's context window, not this one. ## 4. Draft the core docs From the survey, draft (do not write yet): - `$DOCS_DIR/STATE.md` — from the