davekilleen / setup
Run first-time Dex onboarding: build the vault structure, capture the user profile and configure MCPs. Use when `System/.onboarding-complete` is absent or the user says 'set up Dex', 'start onboarding'. Not for the post-onboarding tour; use `getting-started`. Not for a mid-life role change; use `reset`.
Set Up Dex
If System/.onboarding-complete already exists, setup is complete. Use getting-started for the
post-onboarding tour or reset for a role or preference change.
One narrow existing-vault repair is allowed: if setup is complete butSystem/.dex/harness-profile.json is missing or Doctor says agent harness capabilities are
OFF, do not restart onboarding. Call inspect_harnesses, show the automatic / on-demand /
guided / unavailable preview and each host's named limits, ask the person to confirm one or more harnesses, then callsave_harness_selection(..., confirmed=true). That tool writes only the harness receipt
through the sanctioned provision transaction and leaves the profile, content and onboarding
marker unchanged.
Otherwise:
Call
start_onboarding_session()fromonboarding-mcpto initialize or resume
the session.Read
core/onboarding/FLOW.mdand follow it as the single source of the
onboarding conversation.
This file deliberately contains no question script, so onboarding cannot fork.
Change onboarding in core/onboarding/FLOW.md and onboarding-mcp, then regenerate
the byte-identical .claude/flows/onboarding.md compatibility copy; never fork the
question script here.