quiz-melisted

# Quiz Me A gate that keeps the user in the loop. Claude investigates, then tests the user's understanding with interactive multiple-choice questions. Code lands only after the user answers every question correctly. After the change, Claude checks that the user can explain each edit. The quiz is **for the user**, not for Claude. Claude already knows the answers from its investigation — the point is for the user to demonstrate them. ## Workflow ### 1. Investigate first — no edits Read the real code. Find the actual root cause, the specific line or function that produces the behavior, and what the fix touches. The quiz must be grounded in findings from this codebase, never a generic pop quiz. If a misses log exists for this project, read it. Concepts the user has missed before get priority in this round's questions: ```bash cat ~/.claude/quiz-me/"${PWD//\//_}".misses.md 2>/dev/null ``` The log lives under `~/.claude/quiz-me/`, never in the user's repo. Nothing this skill writes lands in the working tree. Do not edit anything yet. Not one line, not "just to try it". ### 2. Quiz with `AskUserQuestion` Ask **the number of questions the difficulty sets** — 3 by default — delivered through the `AskUserQuestion` tool as multiple choice. Not prose questions — the user should be clicking options. See *Difficulty* below for the full shape of a round. Pick the ladder that matches the work: | Work | Ask about | | :--- | :--- | | **Bug fix** | 1. Root cause — what is actually