Repeated Work Should Become a Check
If a task keeps coming back often enough to need reminders, it usually wants a small rerunnable check instead of more memory and coordination.
Some work looks small right up until you notice how often it comes back. Did the doc still ship with placeholders. Did the repo still make first use obvious.
Did the deck still bury the real point in slide six. Did the release-note skim still miss the change that mattered. Those tasks do not usually fail because people are lazy. They fail because the work depends on memory, timing, and somebody noticing the same pattern again.
A good check replaces memory with a rerun
That is why I keep liking tiny utilities that act more like checks than like advice. doc-ship-check is useful because it does not just remind you to look for common doc problems. It lets you rerun the review before handoff.
repo-onramp-check is useful because it does not just say onboarding matters. It turns first-run quality into something you can inspect again. tiny-deck-linter is useful for the same reason. A deck still needs judgment, but a few common failures can be surfaced before the meeting instead of inside it.
The real gain is fewer reminder loops
Reminder-driven work sounds light, but it is often expensive in a hidden way. Someone has to remember the check. Someone has to repeat the standard.
Someone has to rediscover the same failure mode when the work is rushed. A small rerunnable check is often cheaper than that loop. It makes the standard visible without requiring the same conversation every time.
This is one reason I like fun side projects
A fun project gets stronger when it captures one repeated annoyance in a form you can rerun. That might be a docs pass, a repo onramp review, a cleaner incident timeline, or a better one-page planning artifact. The useful part is not that the project exists. The useful part is that the next time the same problem shows up, you do not have to start from memory.
The bar I care about
I do not need every repeated task to become a tool. I do want repeated review work to ask a blunt question: should this still depend on reminders, or is it ready to become a check. That is usually when a small repo stops feeling like output and starts feeling like infrastructure for the next run.