Your List, Tickable
Open items from TODO.md become a page you tick off
Your to-do file's open items are turned into a published page with a tick box and a note field for each. You work the list by clicking, not by editing a file.
Open items from TODO.md become a page you tick off
Your to-do file's open items are turned into a published page with a tick box and a note field for each. You work the list by clicking, not by editing a file.
Items sit under Yours, Decide, Build, Backlog and Ongoing
Every item belongs to one of five groups: things only you can do, decisions you owe, work Claude can build, later work, and long-running items. The group decides how a tick is handled afterward.
Lines the page couldn't read are counted, not hidden
The status bar reads like "18 open · 3 unparsed" when some lines in the file couldn't be read, and each one is named with its line number and the reason. A confident number never quietly drops real work.
The copy button stays on screen as you scroll
Copy my replies sits in the pinned status bar as well as at the bottom, so on a phone you never scroll the whole list to find it.
Add a note to any item as you tick it
Each item has an optional note, so an item can come back as "done, but the old key still works until Friday" rather than just a tick.
Ticks and notes follow the item, not its position
Ticks and notes are saved against each item's title, not its number. When the list is renumbered, nothing slides onto the wrong item. Rewording an item clears its tick, since it is usually a new item.
The page updates at the link you already have
The page is always republished to the same link, so your saved ticks and notes and your open tab stay put.
Ticks on things only you can do are archived as-is
A tick on a Yours or Decide item, like revoking a key or answering a question, can't be checked from the code, so it goes straight to the archive with your note.
Ticked build work is verified before it's archived
A tick on Build, Backlog or Ongoing work starts a check against the actual code and history, like a matching commit, a file, a passing test or a merged change. Only what holds up gets archived, with the evidence.
If the work isn't there, the item stays open with a note
If the work isn't really there, the item stays on the list exactly where it was, with a dated note saying what was found. Nothing is archived on a tick alone.
If a reply could mean two items, you're asked which
Ticks are matched back to items by title. When a title could match more than one item, both are named and you choose, because archiving the wrong item can't be undone.
Finished items move to a monthly archive with the evidence
Done items leave the live list for a monthly archive file, word for word, with the date, your note and what proved them done. The reasoning behind past work stays searchable.
Notes and rules go to the docs, not the to-do list
A root cause, a workaround or a standing rule is moved to the document that owns it instead of sitting in the list as fake work. What stays is real, open work.
Pasting the same reply again changes nothing
Anything a reply names is already gone from the list after the first paste, so pasting it a second time is harmless.
Turns a to-do file full of old history into a clean list
For a to-do file that has grown into a log of finished work, a one-time adopt step first reports how many items are done versus open before anything changes.
Every supposedly open item is checked against the code
Before the list is rebuilt, each open item is checked to see whether it was quietly finished already. Items that turn out to be done go to the archive instead of staying on the list.
Old entries move to monthly files, proven identical
Past entries are split into monthly archive files by their own dates, and every section is compared byte for byte before anything is written. If one doesn't match, nothing is written at all.
You get a report of where each item went and why
The adopt step ends with a report of what was already built, what was really a note and moved to the docs, and which group each remaining item landed in.
A private link, a local file, or your Wi-Fi
Your project picks where review pages go: a private claude.ai link, an HTML file that opens in your browser, or that file served on your home Wi-Fi so a phone can open it. Nothing is ever uploaded or tunneled in the Wi-Fi mode, and the server stops when the review ends.