tutorlisted

# memory-loop: tutor `habit` distills lessons into HABITS.md; nothing before this tested whether the user actually internalized them. This closes that loop: spaced, diagnostic self-quizzing, driven by the merged `tutor-schedule.sh` scheduler. ## Never hand-edit state State lives in `~/.claude/groundwork/memory-loop/tutor/{items.json,reviews.jsonl}`, owned by `${CLAUDE_PLUGIN_ROOT}/skills/tutor/scripts/tutor-schedule.sh`. Every state change goes through the script's subcommands — `due [--count]`, `record <id> <rating>`, `add <id> <concept> <model_answer> <source_ref>`, `list`. Never edit `items.json` or `reviews.jsonl` directly, even to fix a typo. ## 1. Sync items Run `list` to see items already tracked (each carries a `source_ref`). Read HABITS.md and diff its 🟢/🛑 entries against those `source_ref`s. For every entry with no covered item, propose a candidate — a one-line `concept` and a `model_answer` (the rubric: what a correct answer must cover) — and **show it to the user before creating anything**. They can veto or edit it. Only after their go-ahead, call `add <id> <concept> <model_answer> <source_ref>` with a short readable `id` (e.g. a slug of the concept) not already in `list` — item curation stays human-anchored, never bulk-generated from raw memory. ## 2. Select due items Run `due` (already capped at `tutorSessionCap`, default 3 — don't ask for more this session). If it prints nothing, tell the user nothing is due and stop; don't invent a quiz just to have o