onboard

/onboard — Interactive Onboarding & Context Loading

Set up your first project, run an interactive interview, generate a personalized _core/identity.md, create your first daily note, then load vault context. Returning users skip straight to context loading.

Usage

/onboard          # First time: project setup → interview → profile → daily → context. Returning: context only.
/onboard --reset  # Re-run interview even if profile exists (skips project setup if already configured)

Flow

/onboard
  ├── _core/identity.md populated + config has real projects + no --reset?
  │   → Returning user → Load context → "Welcome back"
  │
  └── First time (no profile OR default projects OR --reset)?
       │
       ├── Phase 1: Welcome message
       ├── Phase 2: Project Setup (if config still has default project-a)
       │   ├── Read config.yaml
       │   ├── Detect default project-a/project-b
       │   ├── AskUserQuestion: project name
       │   ├── Edit config.yaml (replace project-a, remove project-b)
       │   ├── Create dirs: docs/{id}/, decisions/{id}/, blockers/{id}/
       │   └── Create 01-index/{id}.md from template
       │
       ├── Phase 3: Personal Interview (3 rounds, 7 questions)
       │   └── Generate _core/identity.md
       │
       ├── Phase 4: First Daily Note
       │   └── Create daily/{today}.md with welcome content
       │
       ├── Phase 5: Load Context
       │
       └── Phase 6: Handoff with "what to do next"

Phase 1: Detect & Welcome

Check if _core/identity.md has been populated (not just the default template):

Read: _core/identity.md

Also read _core/config.yaml to check if projects are still defaults:

Read: _core/config.yaml

Detection logic:

• Returning user: _core/identity.md is populated (has a real role, not placeholder brackets) AND config does NOT contain id: project-a AND no --reset flag → Skip to Phase 5 (Load Context). Greet with:

  Welcome back! Loading your vault context...

• First time or --reset: Continue to Phase 2.