The bigger story here is: checklists, checklists, checklists. They’re underrated!
One that seems close is ForeFlight (demo: https://www.youtube.com/watch?v=d05_ZQMm6Zo&t=23s), but it's just one feature of a much larger app, is mobile only, and obviously targeted at aviation.
I'm looking for similar functionality but more IT-oriented (or at least generic, not referring to airplane models, etc.) and preferably with an offline desktop "client" (it is especially critical that you have your checklist library available if the whole corporate network is down, for example) or, barring that, at least a desktop-friendly web UI.
Honestly, if I knew there was a market for this, I would build it. It's either a great opportunity or the market isn't big enough.
It's not a software engineering challenge. The minimal features are textbook basic CRUD. The essential UI will be well-supported by any framework. Even the challenges when you branch out are solved problems. Device sync, sharing, backups, etc all have some off-the shelf solution or are solved in another space you can look at.
It's a product design / UX / whatever you want to call it problem. Within the set of choices that are easily available to you in the software engineering world, you have to make the right ones! Most people won't naturally make good checklists. How do you help them? One of the biggest (maybe single biggest) issues with checklist is using them at all. How do you get compliance up? How do you handle "skipping" items? Do you go with read/do or do/confirm? How do you keep checklists up-to-date (critical for emergency checklists). It would be very easy to get this stuff wrong.
It also hits a weird spot in the market. What would people pay for this? I don't think you hit enough users for "free" and then my guess is it's a really weird curve with some people paying $1 and then a minority paying like a lot ($100?). I don't know, that's a total guess. Just bringing this up to cover "why isn't a company already doing this?".
Not to be discouraging! Just don't take it as a software engineering challenge. If you're experienced and working on your home turf, it will be easy. The hard thing will be making the right easy thing. Best way to do that is to solve your own problem btw. Maybe start with a "I crashed the server" checklist or something.
If anyone wants to take a stab, the essay that the book "The Checklist Manifesto" is based on would be a good start. The book itself is a bit verbose, but would be worth it if you get serious. I'd also chat for 30 minutes or answer random questions for anyone who's going to make something. My email is my last name at gmail.
Perfect for do-check lists.
[0]: https://apps.apple.com/de/app/daily-checklist-checkyourlist/...
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 proposing a spec for to-do lists.
1. Type it into a file.
2. Print it onto a piece of paper
3. Put a mark by each item with a pen as you finish it.
I have a small sticky note pad on my desk. When we have a meeting about features, I jot down my todos. In some cases, I may do a screengrab, or submit a bug report (to myself), but, most times, it’s the PostIt.
When I’m done with a task, I crumple the note, and drag it into the trash can.
The number of times I've missed a step on a paper checklist because I was on autopilot is ... non-zero
You can create an issue with a checklist in it by pasting in the following:
- [ ] Item one
- [ ] Item two
And if you want to duplicate a checklist, you can copy and paste in a full block of markdown.
Another comment mentioned an offline backup. And I agree. But it's also easy to go from having a month old offline backup to a year old to...