Thanks for sharing this! NotePlan is based on notes. I can't quite imagine how you mean this? You can run review filters to extract tasks from notes and have them summarized in a list independently of the notes. Can you elaborate what you want to achieve? Similarly in apps like things 3, you *have* to create a task within a specific "area". Such as "today", "someday", etc. The equivalent of this in NotePlan is a note - like you said a note per "list". Similar to what Rob Grace wrote, you might be looking for something like an "inbox" list where you can add tasks, which is actually "just" a note containing a list tasks in the sidebar?
Strictly speaking, what you're suggesting would break the whole paradigm on which NotePlan is based: the note "database" being a collection of dated and "regular" MarkDown note files. But maybe you're looking for an Inbox? This was discussed recently, and implemented in the plugin architecture ("/int"). Additional plugin commands can be then be used to re-file those to regular notes as needed Or you can just create an "Inbox" or "!Inbox" note to capture all the loose tasks that you create
It is possible to achieve this by using notes as lists/inboxes for tasks. However, to fully productize this use case, you may consider a solution like: a task list that contains all tasks and allows you to add tasks from that list. The NotePlan equivalent would be the ability to create tasks from the "Review" section, and those tasks created there would be independent of any specific note. My ideal task management app (for which NotePlan appears to come the closest) is an app in which Tasks, Notes, and Calendar Events are independent entities with their own specific views/workflows, but which can optionally be linked (eg, Tasks can be embedded in Notes if desired, and Notes can be embedded in Events if desired).