Skip to content
anymind

Guide ·

Turn Your Notes into Flashcards with FSRS

Most notes are written once and never read again. A modern scheduling algorithm — and one slash command — can change that.

There is a quiet tragedy in most note systems: the better you get at capturing, the larger the pile of things you will never look at again. Notes are written in a moment of clarity, filed with good intentions, and then forgotten — not because they stopped mattering, but because nothing ever brought them back.

Spaced repetition fixes exactly this. It is one of the most consistently replicated effects in learning research: reviewing material at increasing intervals, right before you would otherwise forget it, produces durable memory for a fraction of the effort of cramming.

What FSRS Actually Does

FSRS — the Free Spaced Repetition Scheduler — is the modern successor to the SM-2 algorithm that powered classic flashcard apps for decades. Instead of multiplying intervals by a fixed factor, FSRS models each card with two quantities: stability (how long the memory lasts before recall probability decays) and difficulty (how hard this particular item is for you).

Every time you review a card and grade yourself — again, hard, good, or easy — the model updates both numbers and computes the next due date. The practical result: easy material gets out of your way fast, hard material comes back sooner, and the total number of daily reviews drops noticeably compared to older schedulers at the same retention level.

Anki adopted FSRS as its modern scheduler for good reason. The algorithm is open, well studied, and tuned on hundreds of millions of real reviews.

The Real Problem Is the Pipeline

If spaced repetition works this well, why does almost nobody sustain it outside of language learning and med school?

Because in most setups, making a flashcard is a second job. You read, you take notes in one app, and then you are supposed to open a different app, restate the idea as a question, paste it in, and file it into a deck. Every step is small. Together they are enough friction that the pipeline collapses within weeks. The note app and the memory app stay two separate worlds, and the bridge between them is you, doing clerical work.

The fix is not more discipline. The fix is removing the bridge: reviews should be scheduled where the note already lives.

One Slash Command in the Outline

This is how it works in AnyMind. Any node in your outline — a definition, a quote, an idea you want to keep — becomes a flashcard by typing /card on it. That is the whole pipeline. The node stays exactly where it is in the tree, with its context above it and its children below it. It simply gains a schedule.

When cards come due, they appear in a review queue. You grade each one again / hard / good / easy, FSRS computes the next interval, and the card sinks back into your outline until it is due again. Because the card is a node, reviewing it never strips the idea of its surroundings — you can always zoom out and see the branch it grew from.

There is also a second mode we call roam: a shuffled walk through your cards with no schedule and no grading. Spaced repetition is for retention; roaming is for serendipity — old ideas resurfacing next to new problems.

What to Turn into Cards (and What Not To)

A few rules of thumb that survived contact with practice:

  • Card the atoms, not the essays. A good card is one fact, one definition, one distinction. If a node needs three sentences, split it — in an outliner that is one keystroke.
  • Card decisions and reasons. "We chose PostgreSQL over MongoDB because…" is worth remembering for years. Meeting logistics are not.
  • Don't card what you can always look up in seconds — unless looking it up interrupts the work that matters (keyboard shortcuts, common API signatures, names and faces).
  • Prune without guilt. When a card stops earning its review time, remove the schedule. The note stays in the tree; it just stops knocking.

Notes That Knock on Your Door

The deeper shift is philosophical. A normal note system is a warehouse: things go in, and retrieval is your problem. A note system with scheduling built in is closer to a colleague: it taps you on the shoulder at the moment a memory is about to fade and asks you one question.

Writing in an outline already forces you to decide what an idea is under and what it contains — structure as thinking. Scheduling closes the loop: the structure you built stays alive in your head, not just on the screen.

If you want to try the whole loop — capture, structure, /card, review — the spaced repetition workflow guide walks through a realistic setup in ten minutes.