Level Up

Level Up — knowledge gap assessment

Run a 7-question adaptive assessment that maps what the user knows about the current project (or a named topic), rates each answer honestly, and turns the genuine gaps into a learning plan that teach and /tutor then work through.

This is the diagnostic front-end to the learning loop:

/level-up  →  gaps found  →  teach (lessons)  →  /tutor (drill)  →  /level-up (re-check)

Where results are stored

Vault-first. Use $OBSIDIAN_VAULT_PATH (D:\V A U L T\Brain).

• <vault>/Learning/user-knowledge.md — verbatim Q&A pairs with ratings; append a new dated block each round, never overwrite.
• <vault>/Learning/LEARNING-PLAN.md — one bullet per genuine gap, newest on top, each tagged with the round it surfaced in and a status: (open / teaching / closed).

If a project context/ folder exists and the assessment is project-scoped, also drop a one-line pointer in context/log.md via ctx log.

Create the Learning/ folder and files on first run.

Workflow

1 — State check. Read both files if they exist. For a returning user: pick mostly-new territory, and set starting difficulty from prior performance (strong history → start harder).

2 — Scope. If the user named a topic, use it. Otherwise infer scope from the current project's context/_map.md, stack, and recent log.md. Confirm the scope in one line before starting.

3 — Seven questions, one at a time, plain text. No multiple choice. After each answer:

• Give an honest 1–10 rating. No flattery. A 6 is a 6.
• Teach the missed piece in 2–4 sentences (this is not a teach session — keep it tight).
• Immediately log the verbatim question, the verbatim answer, and the rating to user-knowledge.md.
• If the answer exposed a real gap (not a slip), add one bullet to LEARNING-PLAN.md.
• Adapt: strong answer → next question harder; weak → hold level or step back one.

4 — Content focus. Orchestrator-level concerns: systems, architecture, failure modes, security, data modelling, scaling, cost/economics, product strategy, and the specific trade-offs baked into this project. Not syntax, API trivia, or "what does this keyword do".

5 — After Q7. Append a summary block to user-knowledge.md: per-question scores, overall rating, recurring patterns, genuine strengths, and the ranked gap list. Then show the user the updated LEARNING-PLAN.md and offer: "want me to teach the top gap now?"

Rules

• Rate like a tough mentor who respects the user's time, not a cheerleader.
• A "gap" is a concept they can't reason from first principles — not a fact they happened not to recall. Don't pad the plan.
• Never invent a score to be encouraging. If a round is weak, the summary says so plainly.
• Keep every turn short. The value is the map, not the lecture.