captain-onboardlisted

# Captain onboard Birth a captain in this repo or workspace. Everything through conversation — the user never touches the CLI. ## Already a captain here? If `.tsubasa/captain.toml` exists, this repo has a captain and `init` will refuse. Run `tsubasa upgrade` instead: it is idempotent and brings a captain built by an older tsubasa up to date (schema stamp, source graph, memory tiers), reporting every change. Then stop, and report what changed. Only run the steps below when there is no captain here. ## Steps 1. **CLI present?** `which tsubasa` — if missing: `uv tool install tsubasa` (fallback: `uv tool install git+https://github.com/ramarahmanda/tsubasa`). If `uv` is missing too, ask before installing it. 2. **One round of questions** (single message, not an interview): - captain name (suggest one from the repo/org name, e.g. captain-<repo>) - role (default: Engineering Director) - domains (suggest 3-5 from what you see in the codebase) 3. **Auto-detect sources** — scan for: - git repos: `.git` here or in first-level subdirectories (workspace mode) - ADR/design/architecture docs: `docs/adr`, `docs/decisions`, `*/docs/*.md` (design docs are usually the highest-value source — do not skip them) - postmortems/incidents: dirs or files matching incident/postmortem/outage Present the proposed source list as a table and confirm in one line. NEVER add credential files, .env, or secret stores as sources. 4. **Scaffold**: `tsubasa init <name> --role