AI prompts for pizza shop owners and managers

I work in running a pizza shop. Help me create one polished menu description that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Create a polished, appetizing tent-card menu description while preserving the dish facts and avoiding unverified allergy claims.

Source material:
"Need a menu blurb by 4 for tonight's special -- table tents go out at 5:30. It's the seared salmon over lemon risotto with charred asparagus, off the dinner menu for one night only. Risotto's got parmesan and a butter finish, so no dairy-free claim, and the crust on the salmon has panko in it, so it's not gluten-free either even though people keep asking. Chef Owen wants it to sound good on the tent card but he will not sign off on any wording that promises 'gluten-free' or 'dairy-free' since we can't guarantee the fryer and prep line stay separate tonight. Make it sound appetizing, not like a spec sheet."

Return only the finished work:
polished menu description

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create a set of prep checklist with tasks that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Turn this rushed voicemail into an ordered event-prep checklist the setup crew can run without checking back with you.

Source material:
"Hey, it's Marcus down in banquets -- sorry for the voicemail, I'm elbow-deep in the Magnolia Room right now. The Whitfield retirement lunch just jumped from 25 to 34 people, still Thursday at noon, but the family called back and added three vegan plates and flagged a severe tree-nut allergy at table 6. They also want the room flipped to banquet-style instead of classroom, and coffee and iced tea both need to be up and running by 11:30 since half of them are heading straight to the airport after. Can you turn this into something Jasmine's crew can just run with tomorrow morning?"

Return only the finished work:
1. prep checklist with tasks
2. timing
3. quantities

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one service recovery response for the guest with an internal follow-up note for the kitchen team that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Write a service recovery response for the guest and an internal follow-up note for the kitchen team.

Source material:
Voicemail from event host Priya Chandran, 12:40pm: "Hi, it's Priya with the Meridian Ventures offsite -- we're at table 6 in the Cedar Room. I flagged twice on the intake form that our CFO doesn't eat red meat, and he just got served the braised short rib along with everyone else. He's being a good sport about it, but I promised our team this lunch would run smooth. Can someone get him something else fast, and can you give me two or three sentences I can read out to him so he knows it's handled? Also flag it for the dessert course -- we can't have this happen twice in one lunch."

Return only the finished work:
service recovery response for the guest with an internal follow-up note for the kitchen team

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one service preference handoff that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Turn Sara's text into a service preference handoff for the kitchen and runner, with a clear step for verifying anything that isn't confirmed yet and routing allergy, medical, or safety-sensitive requests to a manager instead of guessing.

Source material:
Sara just texted from the floor: "Table 8, the Delacroix anniversary reservation, wants the grilled chicken with the pan sauce on the side and no spicy garnish on anything -- they've said it twice. Pickup's 12:30, private room upstairs. Can you get something to the kitchen and make sure the runner knows before it goes out?"

Return only the finished work:
1. service preference handoff
2. safety escalation rule

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one inventory variance summary that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Turn today's milk count into a variance summary Yolanda can act on before Thursday's order.

Source material:
"Ran the Tuesday count before the walk-in delivery -- we're supposed to have 8 cases of 2% milk from Friday's order, only 5 are on the shelf. Invoice from Vendemos Dairy says all 8 shipped and got signed for. Nobody flagged a shortage at receiving. Weekend brunch used more milk than usual with the omelet station running both days, so some of it could just be usage, but that's still a three-case gap and the delivery receipt for Friday is missing from the binder -- Felix usually files those. Need something I can hand to Yolanda before the Thursday order goes in."

Return only the finished work:
1. inventory variance summary
2. likely data gaps
3. follow-up questions

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me review the workplace material below and produce one menu feedback analyzer I can use before editing or sending it.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Turn a batch of guest comment-card notes into a format the dining team can act on before the next staff meeting.

Source material:
"Went through Saturday's comment cards for the Hartwell wedding block plus the regular dinner service -- three people said the prime rib was over-salted, table 14 said their entrees came out cold twice before they got food, one guest raved about Marisol's dessert cart and specifically asked for her by name, and we got two complaints about the breakfast buffet line backing up past the elevators before 8am. Can you turn this into something I can bring to the Tuesday staff meeting?"

Return only this review:
menu feedback analyzer

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one shift prep brief that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Build a reusable shift prep brief format the floor can act on without follow-up questions.

Source material:
Voicemail from Chef Dana Okafor, left for shift lead Priya Nandy at 4:52 PM: "Hey Priya, it's Dana, calling before I lose signal in the walk-in. Quick rundown for tonight. We've got the Okonkwo anniversary party, fourteen tops, table 12, they're on the books for 7:15 and the salmon special's the anchor dish for that table. Table 4 is the Thursday book club, nine of them, they usually turn fast so keep an eye on it. One thing I couldn't pin down -- the BEO says someone at table 12 wants the horseradish cream on the side, but I don't know if that's the whole table or just one guest, so somebody needs to confirm that with the host before we fire it. Miguel called out sick, so we're down to four servers for what's shaping up to be a ninety-cover night -- figure out who's covering his section. And Sweetgrass Bakery just texted, the dessert delivery's running behind, now saying six-forty instead of six, so the first hour we're eighty-sixed on the tiramisu and the plated cheesecake. Get something out to the floor before doors open at six."

Return only the finished work:
1. shift prep brief
2. role-specific notes
3. verification checklist

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one repaired service handoff prompt that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Inspect the weak service handoff prompt provided. Identify what is missing, use AI to repair that prompt, then review and edit the AI-repaired prompt. You are not creating a brand-new prompt from scratch. You are repairing the weak prompt provided. The repaired prompt must include role, workplace context, task, boundaries, output format, completion criteria, review rules, and a "STOP FOR NOW" escape phrase (a line that tells the AI when to stop and summarize instead of continuing).

Source material:
Write a note to the kitchen about tonight's Kessler baby shower, they just added six more guests and want the dessert course moved up earlier, just get it sorted before service starts.

Return only the finished work:
repaired service handoff prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one reusable service-preference handoff prompt that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Create a reusable dining handoff prompt for menu preferences, service timing, prep notes, and verification steps. Route allergy, medical, or safety-sensitive needs outside this workflow.

Source material:
A sticky note stuck to the pass, in Colette's handwriting: "Table 3, party of 6 -- hold all entrees till their last 2 show up, should be ~6:15. Beet salad swap: olive oil instead of balsamic glaze, she says it's just too sweet, NOT an allergy. Somebody confirm w/ kitchen before anything fires. -- C"

Return only the finished work:
reusable service-preference handoff prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one dining experience scorecard with a rating scale for each metric that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Create a dining experience scorecard the shift leads can run every week without extra explanation.

Source material:
"Hey -- before Monday's ops huddle I need one scorecard we actually use every week, not another one-off spreadsheet. Priorities: how long the omelet line ran past 9am in the Atrium Cafe (twenty-two minutes, twice last week), whether the salad bar's allergen labels matched what was actually in the pans that day -- after the July 14 mix-up on the walnut dressing I don't want a repeat, guest comment scores from the twelfth-floor executive dining room, food waste pounds logged at close, and how fast Xavier's crew turns around a plate that gets sent back. For each one I want to know where the number comes from -- POS, comment cards, a walk-through note, whatever -- and how often we're actually supposed to look at it. Put together something I can hand to the shift leads without walking them through it every single week."

Return only the finished work:
1. dining experience scorecard with a rating scale for each metric
2. data source behind each metric
3. weekly review cadence for shift leads

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one safer revised service handoff draft that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Review an AI-generated service handoff draft for accuracy, missing context, unsafe assumptions, unsupported promises, and human review needs. Then produce a safer revised version. As a Lead deliverable, also write a short review standard your team can reuse: what to always check, what to never accept, and who signs off.

Source material:
You asked your AI tool to draft a guest-facing note for the Ferraro family's dinner tomorrow night, celebrating grandmother Rose's 80th birthday, after the family added a last-minute nut-allergy request for her. Here is what it wrote: "Great news -- the kitchen has been fully briefed and the entire dinner service for your party has been prepared in a completely nut-free environment. Rose can enjoy every course on the menu with zero risk of cross-contact. We've also gone ahead and swapped the almond-crusted chicken for a walnut-free plate so there's nothing on the table she needs to worry about. Please let her relax and enjoy the evening -- we've got this fully covered."

Return only the finished work:
safer revised service handoff draft

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in running a pizza shop. Help me create one service handoff escalation branch plan that I can review and edit before use.

Relevant context:
- Role: Pizza Shop Owners and Manager
- Work context: You build the weekly prep list, juggle third-party delivery apps against your own online orders, and answer a one-star review before it scares off the dinner rush.

Task:
Work through a changing service handoff scenario. Create a branch plan for what to do if the facts change, what to ask next, what to draft, and when to escalate. As a Lead deliverable, add a short team standard: the rule others should follow, who owns review, and one signal that tells you it is working.

Source material:
The Friday banquet in the Birchwood Room just had its headcount change from 40 to 58 with three tables added late, and the client's event coordinator, Simone, is asking whether the vegetarian entree can be stretched to cover a larger vegan block too. The kitchen needs a short prep note before the 5:30 shift so plating doesn't fall behind.
Branch 1: Simone's vegan confirmation doesn't come through until 4:45, twenty minutes before doors, and Chef Ortiz needs a fast way to confirm exactly how many vegan plates to fire without holding up the rest of the line.
Branch 2: A seated guest stops banquet captain Renee on her way through the room and asks why the card at table 9 doesn't match what she was told when she RSVP'd, wanting a quick answer that doesn't get into headcount or seating logistics.

Return only the finished work:
service handoff escalation branch plan

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.