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.

Display welcome message (for new users):

Welcome to PM-Kit!

I'm your AI-augmented knowledge partner for technical PM and engineering work. Let me get you set up — this takes about 3 minutes.

We'll do three things:

1. Set up your first project
2. Learn how you work (7 quick questions)
3. Load your vault context

Let's get started.

Create session tasks for progress tracking:

Task 1: "Set up first project" (activeForm: "Setting up first project...")
Task 2: "Complete onboarding interview" (activeForm: "Running onboarding interview...", blockedBy: Task 1)
Task 3: "Generate personal profile" (activeForm: "Generating personal profile...", blockedBy: Task 2)
Task 4: "Create first daily note" (activeForm: "Creating first daily note...", blockedBy: Task 3)
Task 5: "Load vault context" (activeForm: "Loading vault context...", blockedBy: Task 4)

Phase 2: Project Setup

Mark Task 1 as in_progress.

Skip condition: If config.yaml does NOT contain id: project-a, projects are already configured. Mark Task 1 as completed and skip to Phase 3.

If config still has the default project-a, ask the user to name their project:

AskUserQuestion

The user can pick a preset or type a custom name via "Other".

After receiving the answer

1. Derive project ID: Use the answer directly as the ID (already lowercase with hyphens). If the user typed a display name with spaces/caps, slugify it (lowercase, replace spaces with hyphens, remove special characters).

2. Derive display name: Capitalize the ID (e.g., my-product → My Product, acme-app → Acme App).

3. Edit config.yaml: Use the Edit tool to:

   • Replace id: project-a with id: {project-id}
   • Replace name: Project A with name: {Display Name}
   • Replace description: Your first project with description: {Display Name} workspace
   • Remove the entire project-b block (the 4 lines: - id: project-b, name: Project B, description: Your second project, active: true)

4. Create project directories:

   Write empty .gitkeep files to:
   - docs/{project-id}/.gitkeep
   - decisions/{project-id}/.gitkeep
   - blockers/{project-id}/.gitkeep

5. Create project index: Write 01-index/{project-id}.md:

   ---
   type: index
   project: {project-id}
   status: active
   ---
   
   # {Display Name}
   
   > {Display Name} workspace
   
   ---
   
   ## Open Blockers
   
   *No open blockers*
   
   ---
   
   ## Active Docs
   
   *No active docs*
   
   ---
   
   ## Recent Dailies (7 days)
   
   *No dailies yet*
   
   ---
   
   ## Recent Decisions (30 days)
   
   *No decisions yet*
   
   ---
   
   ## Manual Notes
   
   %% Add your own notes below — this section is preserved during updates %%

Mark Task 1 as completed.

Phase 3: Interview (3 Rounds)

Mark Task 2 as in_progress.

Skip condition for --reset: If --reset flag is set but projects are already configured (no project-a in config), skip Phase 2 but still run the interview.

Use AskUserQuestion for each round. All 3 rounds use a single AskUserQuestion call each (multiple questions per call).

Round 1 — Who Are You

Ask these 2 questions in a single AskUserQuestion call:

Round 2 — How You Work

Ask these 3 questions in a single AskUserQuestion call: