spaced-reviewlisted

# /spaced-review **Input (optional):** a note in `$ARGUMENTS` — e.g. a specific topic, day, or "just week 1" to narrow the pool. If absent, pull from the full pool described below. ## Steps 1. If `state.json` doesn't exist, or no day anywhere has `status: "done"` yet, tell the user there's nothing to review yet and stop. 2. **Build the eligible pool**: every day across all months with `status: "done"`. Note that no original quiz transcript is persisted — `/spaced-review` re-derives fresh questions from each candidate day's own materials (`coding_problems.md`, `learn.md`, and, if present, `flagged_questions.md` / `confusion_notes.md`), rather than repeating the exact same wording as the original `/done` quiz. 3. **Prioritize by due date first, then by weight:** - Days whose `srs.next_review_due` is today or earlier (or `null`, meaning never reviewed — always due) come first. This is what makes it genuinely spaced, not just recency-sorted. - Within that, weight further toward: `confidence: "struggled"` or `"shaky"`, `has_flags: true`, non-empty `confusion_notes`. - If `$ARGUMENTS` names a topic/day/week, restrict the pool to matches first, then apply the same prioritization within it. - If nothing is due yet and the user didn't name a specific target, say so plainly and ask if they want to review ahead of schedule anyway rather than silently picking something. 4. Pick a handful of questions (aim for 4-8 unless the user's note implies otherwise) spanning a few