Tag
8 posts
Why a folder of plain text files outlives every task app you will ever try: portability, search, version control, and zero lock-in, plus the honest tradeoffs (no reminders, no sync magic) and the minimal setup that actually sticks.
A copy-paste daily planner template as one markdown file: three priorities at the top, time-blocked hours in the middle, a capture section for stray thoughts, and a shutdown ritual at the bottom, plus a filled-in example showing the file after a real day.
A markdown kanban board is one file where headings are columns and checkbox lines are cards: Backlog, Doing, Done, with a WIP limit noted under Doing. Cards move by cut and paste, Git history becomes your audit trail, and the board stays readable in any editor forever.
Copy-paste markdown meeting notes templates for a general meeting, a 1:1, a standup, and a client call. Each one ends in checkbox action items with an owner prefix and a due date, so follow-ups stay greppable weeks after the meeting.
A weekly review template you can paste into any markdown editor, built on the GTD review sequence: inbox sweep, projects review, next actions, waiting-for, calendar look-ahead, and a shutdown step, plus timing guidance and the mistakes that make reviews slip.
The complete markdown checkbox reference: exact `- [ ]` and `- [x]` syntax, the space-after-bracket and list-only rules, 2-space nesting, where checkboxes render and where they are clickable, plus a gotchas table for the mistakes that turn tasks back into raw text.
Five markdown todo list templates you can paste into any editor: a daily list, a GTD inbox with projects, a weekly review, a kanban board, and meeting notes with action items, plus the syntax gotchas that silently break checkboxes.
Markdown task management is a workflow, not a tool. This guide covers the syntax conventions, the apps that respect plain text, and the rules that keep a markdown task list from turning into a second-job file.
