A recurring task is usually treated as a scheduling feature. In practice, it is a system design feature.
When a task reappears automatically, you remove one tiny planning decision from tomorrow. That sounds small until you do it for dozens of routines.
Good recurrence is boring
The best recurring task behavior should disappear into the background:
- check something off
- trust it will come back when it should
- continue planning
No maintenance. No fragile rules.
Tag-driven recurrence
Philo uses inline tags like #daily, #weekly, and #3days.
The task carries its own recurrence logic, right where you wrote it.
That keeps behavior obvious and editable in plain text.
Outcome
The value is not a prettier checklist. The value is a calmer planning surface where recurring obligations manage themselves.