File
SMF·ROUTINE
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·ROUTINE

Can a prompt replace Routine?

Tasks & to-dos — personal tasks, routines and daily planning

Almost Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$12/moSource: routine.co · Checked on July 31, 2026
Per year
$144
Build time
One sitting
Votes
0 votes
YesAlmost (checked)Not yet

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: cross-device reliability and workflow polish
Exhibit Q Questions

Verdict

Turning a line in a note directly into a scheduled task — type a note, select a line, convert it to a task with one action, then drag it onto your calendar — is a real weekend build combining this catalogue's notes and calendar-scheduling approaches into one flow. What doesn't survive: Routine's specific polish in making that conversion feel instant, and its multi-calendar-provider support.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a tool that merges freeform notes with task scheduling: write a note, convert any line into a task with one action, then drag that task onto a calendar to time-block it — combining this catalogue's notes-taking pattern with its Amie entry's drag-to-schedule mechanic into one flow. Use Next.js/TypeScript with Postgres and the Google Calendar API (OAuth) for the calendar side. Build a simple daily-note editor, one Markdown note per day, like a running log. Let the user select any line of text and convert it to a task with a keyboard shortcut or button — this creates a linked task record referencing back to the source note line, without deleting the original text. Show tasks not yet scheduled in a sidebar list, and let the user drag any of them onto a weekly calendar view to create a real Google Calendar event at that time, the same transactional drag-to-schedule mechanic as the Amie entry. Mark scheduled tasks as such in both the note and the task list. Do not build multi-calendar-provider support, native cross-platform apps, or team-shared notes — those are out of scope; this is a single-user, single-calendar-provider tool combining two patterns already described elsewhere in this catalogue. Needs a Google OAuth app (free to register) with Calendar API access, plus hosting and a database.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 polish in making note-to-task conversion feel instant
  • B.2 multi-calendar-provider support
  • B.3 native cross-platform apps
  • B.4 team-shared notes and tasks

Prior art

Exhibit C — Why people still pay: cross-device reliability and workflow polish

Converting a line of text into a task record is simple; making that feel genuinely fast and natural as part of a daily writing habit, without breaking flow, is real interaction-design refinement.

Questions

How is this different from the Amie build in this catalogue?

Amie's build starts from a plain task list; this one starts from freeform daily notes, where any line can become a task with one action, then gets scheduled the same drag-to-calendar way.

Does converting a note line to a task delete the original text?

No — the task is a linked record referencing the note line, so your daily note stays intact as a readable log even after tasks are pulled out of it.

Does it support Outlook or Apple Calendar?

No — only Google Calendar, matching this catalogue's other calendar-integration entries' honest single-provider scope.

What does it cost to run?

Hosting, a database, and the Google Calendar API's free tier — typically a few dollars a month or less.

Receipt

Already built this yourself?