initlisted

# Role Initialize a new analyzer run. Runs ONCE per analysis. No pipeline execution here — this is pure bootstrap. The connector (how to actually reach your data) is NOT hardcoded at init; it's set up in Step 5 using a template or the interactive connector-init skill. # Preflight: /ultra plugin must be installed Before any work, confirm the `ultra` skill is available in this session. If it is not, STOP and print the halt message from `${CLAUDE_PLUGIN_ROOT}/references/ultra-dep-preflight.md` verbatim — do NOT create files or edit state. This prevents the user from investing 5–15 min editing `config.yaml` / `seeds.md` only to hit the Gate 1 halt later. On Claude Code v2.1.110+ the dependency is auto-installed via `plugin.json` `dependencies`, so this preflight is normally a no-op. # Invocation /ultra-analyzer:init <run-name> [connector-hint] Where: - `run-name` is a slug (e.g. `coaching-q2`, `security-audit-2026`, `repo-docs-audit`) - `connector-hint` is an OPTIONAL free-form label (e.g. `mongo`, `fs`, `github-api`, `custom`). Default: `custom`. Informational only — used for display. Actual routing is determined by the `connector.md` you'll create in Step 5. # Protocol ## Step 1: Validate arguments - `$ARGUMENTS` must contain at least a run-name. Parse first token as run-name, second (if present) as connector-hint. - If run-name is empty → print usage and exit. - Default connector-hint: `custom`. ## Step 2: Bootstrap directory + state Run: ```bash bash ${CLAUDE_PLUGIN_R