A spoken method for turning kitchen constraints into a weekly menu.

Voice Prompts for Recipe and menu planning work best when the constraints arrive before the dishes. Start by saying how many people you feed, how many days the plan must cover, how much time you have on each day, and what equipment you are willing to use. Add the limits that actually shape a menu: no oven on weeknights, one shopping trip, leftovers used on Thursday, and a budget range rather than a precise number. Say these constraints in plain sentences and ask the assistant to treat them as fixed. A menu that ignores your Tuesday schedule is not a plan; it is a wish list with ingredients.
List what is already in the kitchen before asking for new meals. Speak the proteins, vegetables, grains, and dairy you have, and note which items are close to spoiling. Say which staples you never run out of, such as rice, pasta, or frozen peas, and which items you refuse to buy again. This inventory does the work that a vague request cannot: it turns the menu into a use-up plan. Ask for dishes that combine what you have with a short list of additions. The result is a plan you can shop for in one trip, not a set of recipes that each demand a separate errand.
State the dietary rules without ambiguity. Say who avoids meat, who cannot eat a specific ingredient, and whether the restriction is absolute or a preference. Distinguish between a household rule and a guest's choice, because a menu that satisfies a guest by removing a staple from every meal often fails the family. Ask for substitutions that keep the dish recognizable, not just technically allowed. If a restriction is severe, say that the dish must be prepared without the ingredient rather than picked out at the table. Clear rules produce a menu you can cook with confidence. Say whether the rule applies to every meal or only to the shared dinner.
Set the effort budget in the same breath as the time budget. A forty-minute recipe can still be too much on a day with a late meeting, and a simple recipe can be perfect on a slow Sunday. Say which nights are for quick assembly, which night can take an hour, and which day is for cooking ahead. Ask the assistant to label each meal with its active time and its total time, so you can see the difference. A plan that looks balanced on paper but puts three long recipes in a row will collapse by Wednesday, and the shopping list will not save it.
Describe the shape of the week, not just the number of days. Say which days are at home, which involve travel, and which include a late return. Note the meals that must be portable, the ones that must reheat well, and the ones that should be eaten fresh. Mention any shared meals with family or guests and any night when cooking is not possible. This calendar turns a generic seven-day plan into a schedule you can follow. When the assistant knows that Thursday is the only shared dinner, it can spend effort there and keep the other nights simple.
Name the leftovers policy. Decide whether the plan should cook once and eat twice, whether lunches come from dinner, and how many repeat meals you can tolerate. Say the answer in the prompt: two repeat lunches, no repeated dinners, and one freezer meal for a busy night. Without this, a menu tends to either waste food or repeat the same dish until nobody wants it. Ask the assistant to show where each leftover goes and on which day it is eaten. A clear leftovers policy is the difference between a plan that saves time and one that fills the refrigerator with forgotten containers.
Say how shopping will happen. One weekly trip, a delivery order, or a midweek top-up all produce different menus. If you shop once, ask for ingredients that stay fresh or freeze well. If you shop twice, say which day the second trip falls on and what it can carry. Mention the store's limits in practical terms: a small shop may not stock a specialty item, so ask for an alternative. A menu that depends on an item you cannot buy is not usable, no matter how good the recipes are. State the shopping pattern before you ask for dishes.
Decide the level of novelty you want. Some weeks call for familiar meals that need no thinking; other weeks are for trying one new dish. Say the ratio, such as five known meals and two experiments, and ask for the experiments to share ingredients with the familiar ones. This keeps the shopping list short and the risk low. If a new dish fails, the week still has five reliable meals. Say which cuisines or flavors your household enjoys and which ones are off the table. Novelty is a dial, not a default, and the prompt should set it before the menu is drafted.
Ask for the menu in the format you will actually use. A day-by-day list with breakfast, lunch, and dinner is different from a list of dinners plus a lunch plan built from leftovers. Say the exact headings, the order, and whether each meal needs a one-line description or a full recipe. If you want a shopping list, say whether it should be grouped by store section and whether quantities should serve the whole week. The output shape decides how much editing you do later, so spend ten seconds describing it before you start speaking. A short example of the shape prevents a long prose answer.
Separate the plan from the recipes. Ask for the week's menu first, then for recipes only for the meals you approve. This two-stage request keeps the first response short enough to judge and prevents the assistant from writing six recipes you will never cook. In the second request, say the serving size, the equipment, and the maximum active time for each dish. If you want a shopping list, request it after the recipes are settled, so the quantities match the final choice. Staging the output is the simplest way to keep a spoken prompt manageable. Approving the menu first also keeps the shopping list from growing.
Use the app's formatting adaptation to get a clean list. Speak the structure as a short sequence: menu table first, then prep notes, then shopping list. Ask for numbers and units in a consistent style, and say whether you prefer cups or grams. If you plan to read the menu at the store, ask for a compact list with quantities beside each item. Voiskey adapts punctuation and formatting to what you are trying to do, so a spoken request for a table arrives as a table rather than a paragraph. Check the first response and correct the shape before adding detail.
Include a fallback for the night that goes wrong. Ask for one pantry meal that needs no fresh shopping and can be made in fifteen minutes. This single line protects the plan against a late meeting, a missing ingredient, or a stove that stops working. Mark the fallback clearly so you can find it without rereading the whole menu. A plan with a fallback is more likely to survive the week than a perfect plan with no spare option. The extra line costs almost nothing to speak and often saves the whole schedule. A fallback that needs no planning is the one you will actually use.
Before you shop, compare the shopping list with what you already own. Read the list aloud and cross off items you have, then add the items the menu assumes but the list forgot. Check quantities, not just names: three recipes that each need half a bunch of herbs may still leave you short. Confirm that perishables appear early in the week and that frozen items have a place to go. If an ingredient appears once in a small amount, ask whether a simpler substitute would work. This check is unglamorous and saves both money and a second trip. Mark the quantities you are unsure about so you can check them at the shelf.
Cook the first meal as a test of the prompt. Follow the plan without improvising, and note where the recipe assumed something you did not have or a step that took longer than stated. If the instructions were unclear, fix the prompt's output request, for example ask for numbered steps with times. If the portion was wrong, adjust the serving size line. One test meal teaches more about the prompt than a page of planning. Record the correction in the template so next week's plan starts from a better brief. Keep the note beside the recipe so the correction is visible the next time you cook it.
Read the menu with the people who will eat it. Ask each person to name one meal they are glad to see and one they would swap. Use those answers to adjust the prompt rather than editing the menu by hand. If a meal is rejected because of an ingredient, add that ingredient to the avoidance list. If a meal is rejected because of effort, move it to a slower day. Household feedback is the fastest way to tune a spoken menu prompt, and it takes less time than defending a plan nobody wants. Write the accepted swaps into the prompt so the next menu starts closer.
Keep the final menu where the household can see it. A plan in a message window is easy to forget; a plan on the refrigerator or in a shared note gets used. Put the menu and the shopping list in the same place, with the fallback meal marked. When you change a day, update the note so the shopping list stays accurate. Anyone who wants to try this workflow can download Voiskey and speak the constraints, the week shape, and the output format into the note they already keep. A shared note also lets anyone add a missing item before the next shopping trip begins.
Turn the first good prompt into a weekly template. Keep the constraint lines, the dietary rules, the leftovers policy, and the output shape, and leave slots for the week's schedule and the pantry inventory. Speak the template once and save the text where you plan meals. Each week, edit the slots and run it again. The template should take less than a minute to fill in, or it will not survive a busy Sunday. A reusable prompt is not a rigid plan; it is a starting point that already knows your kitchen. Keep the template short enough to fill in while the kettle boils.
Track what the template gets wrong. Keep a short list of corrections: portions too large, too many long recipes, a shopping list that missed a staple. Add one constraint for each recurring problem and remove constraints that never change the result. After a month, the template should need fewer edits than it did in the first week. If a change makes the plan worse, revert it and note why. Templates improve through small, recorded adjustments, not through a complete rewrite every time the menu disappoints. The list should name the week and the meal so the pattern is easy to spot.
Build a small rotation of templates for different weeks. A normal week, a holiday week, a travel week, and a use-up week are different problems. Give each one its own short brief rather than forcing one template to cover every case. The holiday template can assume more cooking time; the travel template can assume no cooking at all. Keep the number small so you can remember which one to use. When a new situation appears, copy the closest template and adjust it instead of starting from a blank prompt. Name each template by the kind of week so the choice takes a second.
Share the template with anyone who cooks in the household. A spoken prompt is only useful if the person planning the week can run it without help. Put the template and a sample menu in a shared note, and ask the other cook to run it once. Compare the two menus and keep the constraints that made both work. The team plan offers shared vocabulary and workflows, which helps when several people plan and shop for the same kitchen. To start, download Voiskey, speak the template into a note, and run it for one week before changing anything. Ask for one comment on what the other cook changed and why.
Voiskey is an AI voice typing app that works in the note window you already use. Press a shortcut and speak the household size, schedule, dietary rules, pantry items, and output shape; the prompt appears at the insertion point with filler words and self-corrections removed, so the menu brief is clean and easy to reuse.
Voiskey learns names, jargon, acronyms, and spelling preferences. Say an ingredient once and it keeps your spelling in later prompts, which helps with unfamiliar produce, regional names, and household shorthand. Check the first menu response for any drift, then correct the term in the brief before you build a weekly template.
Yes. Voiskey places text at the insertion point in any app or text field, so you can dictate the menu brief into the note you already use. It adapts punctuation and formatting, so a request for a day-by-day table arrives as a table. Keep the prompt and the menu in the same note for the next week.
Voiskey supports more than one hundred languages and translation. You can speak the kitchen constraints in one language and ask for the menu in another, then request the shopping list in the language you use at the store. Review ingredient names with a fluent cook before shopping, since regional terms for the same item can differ.

Download Voiskey for Mac and Windows and speak your next weekly menu brief.
Use it across macOS, Windows, iOS, and Android