cissp-onboard

name	cissp-onboard
description	Run (or re-run) the background calibration that writes kb/my-background.md

Walk the user through the background calibration. This is the same flow described in AGENTS.md under "First-session onboarding", but invokable on demand — useful when:

• kb/my-background.md doesn't exist yet and the user wants to set it up
• The user's background has changed (new role, exam date set/rescheduled, weak areas shifted) and they want to refresh
• The user wants to add more context after a few study sessions

Steps

1. If kb/my-background.md already exists, show the current contents first and ask: "I see you already have a background file. Want to (a) update it in place, (b) replace it entirely, or (c) cancel?"

2. Ask the questions conversationally, one or two at a time:

   • Their professional background (security / IT / audit / dev / student / other) and years of experience
   • The CISSP target exam date (if known)
   • Domains they feel weakest about, or the topics they're most nervous about
   • How they prefer to study (quick quizzes, deep reading, scenario practice, mixed)
   • Anything else the agent should know to calibrate explanations

3. Write the answers to kb/my-background.md using this format:

   # My Background
   
   *Last updated: YYYY-MM-DD*
   
   ## Professional context
   - <role / years / industry>
   - Already familiar with: <topics>
   - Less familiar with: <topics>
   
   ## CISSP plan
   - Target exam date: YYYY-MM-DD (or "not set")
   - Weakest-feeling domains: <list>
   - Preferred study style: <free text>
   
   ## Notes for AI assistants
   - <anything else useful for calibrating answers>
   

4. Confirm and offer next step:

   • "Saved to kb/my-background.md — edit anytime."
   • "Want to also set your exam date in the webapp at /settings so the study plan paces you?"
   • "Want a quick /cissp-status snapshot now that I know your background?"

Rules

• Keep questions short. Never more than 4-5 total.
• Accept "skip" gracefully on any question.
• Do NOT proceed to write the file if the user hasn't answered the core questions (role + weak areas).
• Never overwrite an existing kb/my-background.md without explicit confirmation (step 1).
• No emoji.