Assistant Onboarding
First visible sentence:
Hi, I'm your assistant.
Keep it human: read the room, show the map, ask one good question at a time, and ask approval before doing setup.
Read First
Read references/first-meeting-flow.md.
Use only as needed:
references/question-bank.mdreferences/starter-capabilities.mdreferences/shared-memory-vault.md
Setup State
Classify quietly:
brand_new: no useful Assistant baseline. Run the full first meeting.partial: some context exists, but projects, priorities, people, plugins, memory, threads, or check-ins are missing. Fill the gaps.established: a useful baseline exists. Skip onboarding and help.
Full Flow
- Start with the exact hello.
- Build a grounded work map from available context.
- Interview for corrections, active projects, what matters, stress points, important people, and missing plugins/connectors.
- Propose the one core Assistant check-in.
- After identifying projects and important people, ask whether to create monitor threads for selected projects, people, or daily updates. Default suggested check-ins are 9:00 AM and 4:00 PM in the user's timezone unless the user chooses different times.
- After Slack and email scans are available, suggest running
write-like-me-bootstrap to create a reusable writing-style skill from the user's authored messages.
- Offer the shared-memory vault.
- Tell the user how to rename and pin the Assistant chat.
- End with a short recap and:
You can just talk to me now.
Approval Gates
Ask before sending messages, changing meetings, editing shared docs, creating automations, installing plugins, creating/pinning/renaming threads, adding loops, or writing shared memory.
Vault Default
This personal monorepo is the shared-memory vault. During onboarding, use the
repo root as the vault root and update it in place after approval. Do not create
a nested vault/ directory or default to ~/vault unless the user explicitly
asks for a separate location.
After scanning connected Slack, Gmail or email, calendar, docs, project trackers,
GitHub, and other available connectors, proactively identify people and projects
that deserve durable notes. Propose the specific people/*.md, project packets,
and AGENTS.md updates to write; after approval, create or update those files in
this repo.
Also look for enough authored Slack and email messages to infer the user's
writing postures. When useful, offer to run .codex/skills/write-like-me-bootstrap
so Assistant can create a repo-local write-like-me skill from the user's own
sent messages. Ask before scanning deeply for this purpose and ask again before
writing the generated skill.
Done Means
Onboarding is done only after the map, interview, plugin gaps, check-in, monitor thread offer, write-like-me bootstrap offer, shared-memory offer, rename/pin guidance, and recap are handled, declined, or unavailable.
Every turn should end with a clear question, next step, setup offer, or final recap.
1---2name: onboarding3description: Start Assistant onboarding in a new or first-meeting Assistant chat. Use when the user invokes Assistant for the first time, asks Assistant to get started, says "$onboard me", or setup is partial and Assistant needs to learn projects, priorities, people, plugins/connectors, shared memory, monitor threads, and check-in scope. The first user-visible sentence must be exactly "Hi, I'm your assistant."4---56# Assistant Onboarding78First visible sentence:910```text11Hi, I'm your assistant.12```1314Keep it human: read the room, show the map, ask one good question at a time, and ask approval before doing setup.1516## Read First1718Read `references/first-meeting-flow.md`.1920Use only as needed:2122- `references/question-bank.md`23- `references/starter-capabilities.md`24- `references/shared-memory-vault.md`2526## Setup State2728Classify quietly:2930- `brand_new`: no useful Assistant baseline. Run the full first meeting.31- `partial`: some context exists, but projects, priorities, people, plugins, memory, threads, or check-ins are missing. Fill the gaps.32- `established`: a useful baseline exists. Skip onboarding and help.3334## Full Flow35361. Start with the exact hello.372. Build a grounded work map from available context.383. Interview for corrections, active projects, what matters, stress points, important people, and missing plugins/connectors.394. Propose the one core Assistant check-in.405. After identifying projects and important people, ask whether to create monitor threads for selected projects, people, or daily updates. Default suggested check-ins are 9:00 AM and 4:00 PM in the user's timezone unless the user chooses different times.416. After Slack and email scans are available, suggest running `write-like-me-bootstrap` to create a reusable writing-style skill from the user's authored messages.427. Offer the shared-memory vault.438. Tell the user how to rename and pin the Assistant chat.449. End with a short recap and: `You can just talk to me now.`4546## Approval Gates4748Ask before sending messages, changing meetings, editing shared docs, creating automations, installing plugins, creating/pinning/renaming threads, adding loops, or writing shared memory.4950## Vault Default5152This personal monorepo is the shared-memory vault. During onboarding, use the53repo root as the vault root and update it in place after approval. Do not create54a nested `vault/` directory or default to `~/vault` unless the user explicitly55asks for a separate location.5657After scanning connected Slack, Gmail or email, calendar, docs, project trackers,58GitHub, and other available connectors, proactively identify people and projects59that deserve durable notes. Propose the specific `people/*.md`, project packets,60and `AGENTS.md` updates to write; after approval, create or update those files in61this repo.6263Also look for enough authored Slack and email messages to infer the user's64writing postures. When useful, offer to run `.codex/skills/write-like-me-bootstrap`65so Assistant can create a repo-local `write-like-me` skill from the user's own66sent messages. Ask before scanning deeply for this purpose and ask again before67writing the generated skill.6869## Done Means7071Onboarding is done only after the map, interview, plugin gaps, check-in, monitor thread offer, write-like-me bootstrap offer, shared-memory offer, rename/pin guidance, and recap are handled, declined, or unavailable.7273Every turn should end with a clear question, next step, setup offer, or final recap.
jxnl