Onboard

What this skill does

Single combined wizard. Reads or writes aios-intake.md (the canonical intake), conducts the 7-question interview if the file isn't filled, then scaffolds the Day-1 file set inline at the end of the run. No separate /scaffold-from-intake skill — this is one flow.

The wow moment: at the end, suggest the closing prompt "Try this — ask me: what should I focus on this week?" The user runs it once. That's the wow. There's no /today skill to save — the prompt itself plants the Mindset framework (Default Shift) for them to internalize.

When NOT to run this

• If the user has already onboarded and wants to refresh: still run, but skip questions already answered (idempotent).
• If the user wants to add a new connection: that's not onboarding — point them at connections.md to edit directly, or schedule a /level-up Phase 2 walk.

Execution

Step 1: Read the intake

Read aios-intake.md. Check which Q1-Q7 sections have content vs. [Your answer here] placeholders.

• All filled → skip Step 2, jump to Step 3 (scaffold).
• Some filled → ask the user: "I see Q1, Q3, Q4 are answered. Want to fill the rest now, or scaffold from what's there?" Their call.
• None filled (fresh clone) → run Step 2 conversationally.

Step 2: The interview (7 questions, hard cap)

Ask one at a time. Write each answer into aios-intake.md as you go (so the user can resume if interrupted).

Q1 — Who are you, what do you sell, who do you sell it to? Identity, offer, ICP. One paragraph each is fine.

Q2 — Paste 1-2 things you've written recently. Don't edit them. This is the only question with a hard rule. Voice samples MUST be pasted, not typed mid-conversation. If the user starts typing fresh prose, refuse:

"Stop — paste it raw. If you type it here while we're talking, the sample is already shaped by our conversation. Open your last email or LinkedIn post in another tab and paste the unedited text. This is the one rule I can't bend."

Ask for two samples. One email, one post. Or two of either.

Q3 — What are your 2-3 biggest priorities for the next 90 days? Quarterly priorities. Push back if they say "grow my business" — make them name a number, a deadline, or a deliverable.

Q4 — Where does revenue actually land, and where is it tracked? Multiple answers OK. Map to Tier-1 Domain 1 (Revenue/Financials).

Q5 — Where do you talk to customers, your team, and the outside world day-to-day? Email (Gmail/Outlook), Slack/Teams/Discord, DMs. Map to Domains 2 + 4.

Q6 — Where do meeting recordings, notes, and important docs live? Map to Domains 6 + 7.

Q7 — What's the one task that eats your week, and where do you currently track work? Capture top_pain (used by /level-up Day-14) + Domain 5 (tasks).

Domain 3 (Calendar) is auto-inferred from Q5: Gmail → Google Cal; Outlook → Outlook Cal. Confirm in Step 3.

Step 3: Scaffold the Day-1 file set

Once the intake is complete, generate these files (or update if re-running). Back up originals to archives/intake-{YYYY-MM-DD-HHMM}/ if any exist.

1. context/about-me.md — from Q1 (identity, role) + Q7 (top_pain). One short paragraph each.

2. context/about-business.md — from Q1 (offer, ICP) + Q4 (revenue model). One paragraph.

3. context/priorities.md — from Q3. Numbered list, one line per priority.

4. references/voice.md — from Q2. Paste samples verbatim with a short header explaining their use ("Match this register when drafting; don't fake voice on external content without showing me first").

5. connections.md — populate the 7-row table from Q4-Q7 answers. Each row gets mechanism: not yet connected, auth: —, last checked: —. The user wires connections on Day 2.

6. CLAUDE.md — fill all {{...}} placeholders. Substitute the user's name, stated priority, voice register summary, and a brief connections summary.

7. squads/*.yml — fill the {{Ton projet X}} placeholders. Parse Q1 (offer) + Q3 (90-day priorities) + Q7 (recurring chore) to extract 1-5 named projects. Present a one-shot confirmation table, not a new question :

   I see these projects in your answers. Mapping to squads :
   
   | Project (inferred) | Suggested squad |
   |---|---|
   | <ProductName from Q1> | builder |
   | <Priority X from Q3>  | shipper |
   | <ChoreContext from Q7> | operator |
   
   Type "ok" to apply, or "change <project> → <squad>" to adjust.
   

   Edit the YAMLs accordingly. Projects not mentioned go to {{À définir}} placeholders that stay editable.

8. Suggested default squad — based on Q1's offer type :

   • Tech product / SaaS → builder
   • Coaching, education, content → creator
   • Consulting / freelance / agency → operator
   • Research / discovery-heavy → researcher

   Add this as a final line in the closing screen : "Default squad : <name>. Activate later with /squad <name>."

9. Model routing preference — based on Q4 (revenue) sensitivity, suggest a default tier in CLAUDE.md "Routage modèles" section. If revenue is mature/comfortable → keep Opus default. If pre-revenue / cost-sensitive → switch the section's "default starting model" line to Sonnet 4.6, with the comment "// inferred from /onboard, change anytime".

Step 4: The closing screen

Print one screen. Compact :

✓ Day 1 done. Your AIOS knows who you are, what you sell, what matters this quarter, and how you sound.

Today: ask me — "what should I focus on this week?"
Tomorrow: pick one tool from connections.md and wire it up (manual MCP install or write a small API script + save references/{tool}-api.md).
Day 3: try /squad <default-squad> to activate your first agent bundle, then /orchestrate runbook-<mvp|contenu|feature> to run a real workflow.
Day 7: run /audit to see your score.

New skills you now have :
  /squad         — activate a bundle of 5-15 specialized agents
  /orchestrate   — run a multi-agent Conductor workflow (5 runbooks)
  /roster        — search the 224-agent catalog for any need
  /cost          — track your LLM spend per project / session
  /snapshot      — save / restore session state across days

When the user runs the closing prompt ("what should I focus on this week?"), respond using only the new context files. Hit:

• 3-bullet priority list, in their voice register from Q2
• Each bullet ties back to a stated 90-day priority from Q3
• Final line: "If I had to pick one thing for Monday, it'd be [X], because [reason from priorities]. Want me to draft the first email? And — where could the Default Shift apply here? To what extent could AI be leveraged on this task?"

The Default Shift question seeds the Mindset framework before /level-up formally introduces it on Day 14.

Critical implementation rules

1. The 7-question cap is non-negotiable. Don't add Q8 in conversation. Step 3 confirmations (squad mapping, default squad, model routing) are inferred from Q1-Q7 and presented as a single confirmation table, not as new questions.
2. Voice paste cannot be skipped. If the user types samples mid-chat, refuse and tell them to paste from real writing.
3. One-shot scaffold. After Step 2 ends, write Step 3 files in a single batch. The squad mapping confirmation (sub-step 7) is the only inline interaction allowed — and it has a default-yes (ok to apply).
4. Idempotent. Re-running with an edited intake refreshes context files; backs up originals to archives/intake-{ts}/. Skips questions already answered unless the user wants to revise. When re-run, don't overwrite squad YAMLs if the user already edited them — only fill remaining {{...}} placeholders.
5. Closing screen is compact. Lists the new skills so they're discoverable but doesn't pitch them.
6. No extra skills generated. Don't scaffold /today, /draft, /connect, etc. The kit ships 8 skills (/onboard, /audit, /level-up, /squad, /orchestrate, /roster, /cost, /snapshot); the user authors more via /level-up.
7. Read-only on references/operator-lens.md. It already ships in the kit. Don't overwrite.
8. No .env writes. Don't ask for API keys on Day 1. Connections come Day 2.
9. Squad placeholders default to {{À définir}} when unsure. Better leave editable than guess wrong.

Verification (for the implementer)

• Cold-test: clone a fresh kit, run /onboard, fill 7 answers, scaffold runs, ask the wow prompt, response cites Q1 + Q3 + Q7 specifically. Generic = fail.
• Idempotency: re-run /onboard with one Q3 priority changed. Expected: only context/priorities.md and CLAUDE.md's priority section update; backup created in archives/intake-{ts}/.
• Voice rejection: type a sample mid-chat. Expected: skill refuses, asks for paste.
• Squad scaffolding: after onboarding, squads/builder.yml (or relevant squad) has the user's named projects in projets_phares: instead of {{Ton projet X}} placeholders. Unmatched squads keep {{À définir}}.
• Closing screen discoverability: a fresh user can name 3 of the 5 new skills after reading the closing once.

Part of Kopern-OS. The Mindset language used in the closing screen comes from references/operator-lens.md — the Kopern-OS 3M Operator Lens. © 2026 Thomas Berchet / Kopern AI. MIT licensed.