Todos

Writing a spec is full of loose ends — "decide on the rate-limit", "check this with legal", "finish the validation rules". A todo is a small marker you drop right where the decision lives, so it's visible in the editor instead of buried in an HTML comment, and counted across the whole project so nothing slips.

Adding a todo

Run /todo from the slash menu and type a short comment. It drops in as an amber chip with a sticky-note icon, right at your cursor. In the file it's a compact inline tag:

<todo comment="decide on the rate-limit strategy"/>

Long comments are shortened on the chip with the full text in a tooltip; a todo with no comment just reads TODO. To change one, alt-click (option-click on a Mac) or double-click the chip — Save updates the comment, Remove deletes it, Cancel backs out.

Seeing every todo at once

Todos are tracked project-wide and stay current within about a second of any edit:

• The TODOs page lists every todo in the project, grouped by file and searchable, with a link straight to the spot in the source.
• A counter next to TODOs in the sidebar shows the project total (hidden when there are none).
• Each file in the Pages tree carries a small amber badge with its todo count.

Todos vs. checklists

Todos aren't the only way to leave a box to tick. The editor also renders standard markdown task lists:

- [ ] validate the request body
- [x] return 401 on missing token

These are clickable checkboxes for items you work through — acceptance-criteria-style checklists. Reach for a task list when you're ticking off steps inside a section, and a <todo> marker when you want to flag a single spot to revisit and have it counted across the project.