Routines

Routines are reusable checklists you run on a rhythm — for example, "Sunday Reset," "Monthly bills review," or "Seasonal yard prep." In HoneyDone, a routine is a template. It never carries state itself. Instead, every time you run a routine, HoneyDone creates a fresh execution and spawns real tasks from the template's steps — so your history stays clean and each run is independently trackable.

How it works

1. Create a routine on /routines. Give it a name and pick how often it runs (weekly, monthly, seasonal, or on demand).
2. Add steps on the routine detail page. Each step becomes a task when the routine runs. Steps can also be plain checklist notes that don't spawn tasks.
3. Run it. Click "Run now" on any routine. HoneyDone creates an execution, spawns one task per task-step, and takes you to the execution page.
4. Check off steps. On the execution page, checking a step marks both the execution step and the underlying spawned task as done. When every step is complete, you can mark the whole routine execution complete.

Why routines (not just recurring tasks)?

A recurring task is a single row that cycles status. A routine is a parent template with ordered steps, so each run produces a fresh set of tasks that can be assigned, prioritized, and tracked independently. You get clean history, source links back to the originating routine, and the ability to edit the template without touching past runs.

Provenance

Every task spawned from a routine execution carries a source_link pointing back to the execution, so you can always see where a task came from.

Guardrails

• Routines cannot have assignees, due dates, or a status. Only the spawned tasks carry those.
• Automation cannot complete tasks. Only a human (or the user clicking a checkbox in the execution view) can complete a step.