I've thought of the same idea. The rough workflow for creation would be (1) create a checklist, (2) publish it to the world as a template, (3) let others fork i

I've thought of the same idea. The rough workflow for creation would be (1) create a checklist, (2) publish it to the world as a template, (3) let others fork it, send PRs, etc. Then the usage workflow is (1) search for a template, (2) instantiate your own copy, (3) use it. As you say, you'd want the list and the checkbox states available offline, and maybe synced elsewhere. Throw in collaboration features like sharing a single checklist ("are we bringing everything we need for the roadtrip? mark items that you've packed" "someone please buy milk, or else I will if it's still on the list when I stop at the grocery store tonight," "has everyone grabbed a task for the next sprint?"), or delegating items to other people ("for tomorrow's presentation, make sure someone has set up the projector"), and it could add the magic that I felt back in 2009 when I realized how amazing git became once GitHub was layered on top of it. The reusable-list idea works for me when I'm traveling. I have a list of stuff I need to do when I leave the house -- turn off the thermostat, make sure the plants are watered, etc. -- and I find it annoying to have to uncheck the old list's items in Google Keep. I'd rather keep the old checked lists and instantiate new ones. The list itself evolves over time, so having the old completed (or not-quite-completed) lists is interesting. Also see this recent item https://news.ycombinator.com/item?id=32552782 https://news.ycombinator.com/item?id=32552782 proposing a spec for to-do lists.