I just use email. Let me explain.
My wife and I semi-asynchronously, find 3-4 recipes each and send each other links/(book,title,pg no) in chat. Then one of us drafts and email, referencing each recipe and the list of required ingredients, and finally sends it to both of us.
We then enter an order online for grocery pickup and stock the fridge. When we wish to make dinner, we reference the latest "menu" email and simply pick one of the items from the list.
Sometimes we'll chain menu items like chili -> chili dogs or tritip -> sandwiches, but for the most part it's operates like a grab bag for the week.
It's easy enough to go back and search for any old "menu" email as far back as we want and because everything is referenced by url or citation, we can add it to the next menu by navigating to the url or pulling the cookbook from the shelf.
The reference system work great during cooking too. I can pull up the recipe on my phone in the kitchen and follow the recipe there, or again, pull the cookbook from the shelf.
The flexibility of email is an advantage here. It works as a substrate for a process rather than railroading the process itself. You see, any app that replaced this would have to handle this specific workflow. It's easier to build a robust workflow on a flexible substrate than on a brittle bespoke substrate like an app.