op-onboardlisted

Use to create or refresh `~/.claude/achron-spine-profile.md` — the personal calibration file capturing the user's Claude subscription, experience level, stack preferences, environment (OS / VCS / plans-dir / currency), project context (typical work / artifact / deploy target / database / team / users / org), working style, output format, and risk tolerance. Fires when the user invokes `/onboard` (essentials), `/onboard --deep` (full ~28-question interview, +2 conditional follow-ups for UI apps), or says "re-onboard" / "update my profile" / "redo onboarding". For a single output-style change, `/explain` (explanation style) or `/effort` (reasoning effort) is the lightweight path — this skill is the full profile interview. For the first-run greeting that points the user at `/onboard`, see the sibling `op-welcome` skill — it owns the file-absence surface so this skill never auto-launches an interview unannounced.
TimTGelhard/ACHRON-spine · ★ 1 · Data & Documents · score 74

Install: claude install-skill TimTGelhard/ACHRON-spine

# op-onboard — personal calibration Captures and maintains `~/.claude/achron-spine-profile.md`. The profile shapes Claude's tone, defaults, and discipline for this user across all projects. ## Mode selection 1. **`/onboard` with no profile yet** → ask **Q2a (experience) first** — it's the branch trigger. "I've never written code" asks one more one-tap follow-up (**Q2-floor** — how simple → `child` / `teen` / `new`); "I steer the AI…" resolves to `vibe`. On `new`/`vibe`/`child`/`teen` → run the **2-question express path** (`questions-express.md`); on a coder rung → run the full **essentials** (10 questions). Either path writes the profile; only the coder path then offers the deep interview. (The first-run *greeting* is `op-welcome`'s job; this mode runs once the user actually invokes `/onboard`.) 2. **`/onboard`** with profile present → re-run essentials. Read the existing profile first; show current values; ask only the ones the user wants to change. 3. **`/onboard --deep`** → if profile is missing, run essentials first, then deep (18 more questions, +2 conditional follow-ups when Q9 = UI-bearing artifact, + 2 opt-in hook prompts). If profile exists, jump straight to deep — but still run the **context-window + effort tune** (step 5) once, so a deep re-run also asks those two questions. 4. **Ad-hoc edits** ("change my push-back to spar with me") → edit the matching profile section directly; don't restart the interview. ## Adjacent files (read on-demand) | File | When | |-