Making Markdown Work for You

A task note can be a scratch pad or a structured document. Markdown is what makes the difference. Once you start writing notes that you'd actually want to read back later — with headers that organize, checklists that track, and links that connect — your tasks stop being reminders and start being reference material. This article is for people who are already using Markdown in their notes and want to go further.


Notes as Meeting Records

A meeting generates decisions and actions. A task note is a natural place to capture both, in a format that doesn't require a separate document.

The pattern: create a task titled for the meeting. In the note, use a ## heading for each agenda item. Under each heading, use bullet points for discussion notes and - [ ] checkboxes for follow-up actions. When the meeting ends, you have a single source of truth for what was decided and who owns what next.

## Q2 Planning Review — 04/01/2026

## Roadmap prioritization
- Agreed to move payment integration to Q3
- Mobile push notifications stays top priority
- [ ] Update roadmap doc with revised timeline — ZWS

## Budget
- Marketing allocation unchanged
- [ ] Get revised headcount numbers from HR before 4/8

## Next meeting
- April 15, 10am CT

The note doesn't replace a project management system. It replaces the friction of opening one just to capture what happened in a 30-minute meeting.


Notes as Reference Documents

Not every task is about doing something. Some tasks exist to hold information — the client's technical requirements, the login credentials for the staging server (in a password manager link, not plaintext), the list of decisions already made on a project so you don't re-litigate them.

Markdown headings make a long reference note navigable. A note with five flat bullet points is a list you have to read top-to-bottom. A note with ## headings is a document you can scan. When you return to a task three weeks after creating it, the difference between those two formats is the difference between a useful reference and a wall of text.


Checklists That Persist

Subtasks are tracked by Principal Task. When you complete a subtask, it registers as a completion and contributes to Task Velocity. A - [ ] checkbox in a note is different: it's a manual checklist that lives only in the note, doesn't affect velocity, and can be reset and reused indefinitely.

That distinction is useful. Subtasks are for work that should be tracked — things you want counted, things with their own due dates, things that might be delegated. Markdown checkboxes are for steps within a single task that follow a consistent sequence — a setup checklist, a publishing workflow, a pre-flight review. When the task completes, you can uncheck the boxes and use the same structure next time without rebuilding it.


Keeping Notes Scannable

Four habits that make a note useful to read back:

Use a heading for every distinct topic. If a note covers more than one thing, give each thing a ## heading. Notes without headings become a continuous block of text that requires reading start-to-finish.

One idea per bullet point. A bullet that contains three clauses is a paragraph in disguise. Split it.

Put the most important information first. Notes are often read quickly in context. The detail that matters most — the deadline, the decision, the blocker — belongs at the top, not buried four paragraphs in.

Use --- to separate unrelated sections. If a note holds information about multiple distinct topics, a horizontal rule provides a visual break that makes it clear where one section ends and another begins.


The Note Is Part of the Task

When a note is well-structured, completing the task and reading its note are nearly the same action. The context is there, the steps are recorded, and the decisions are documented as they happened — not reconstructed later. A task list tracks what needs to be done. A task list with good notes tracks what needs to be done and why, in a format you can hand off, revisit, or close with confidence. If you want a refresher on the syntax that makes this possible, Richer Notes with Markdown covers it all.