Plan a party

Extract the ZIP. Copy its lc-party-plan folder into ~/.claude/skills/ for Claude Code or ~/.codex/skills/ for Codex, then refresh the native app. Ask for the skill by name and answer its questions. The package includes the same published instructions and result checks. Native host execution is not yet verified.

For Claude web, use the connector or copy the prompt. Keep private details in your assistant.

Copy, paste into your assistant, then answer its questions. No form or account is required here.

Open in ChatGPT ↗

Already connected? Copy the public starter below and paste into Claude. Keep private details in the chat.

Required details are present. Review the result before using it.

Saved only on this device. Copy counts contain the skill ID, never your text.

## LazyCoder conversation guide (conversation-v2)
1. Start a conversation, not a form-filling task. Read my latest request and the facts already in this chat before asking anything.
2. Ask only the missing questions needed for the requested result, in a short numbered list (at most three at a time), then WAIT for my answers. Use a native question tool if available; plain chat works too. Never ask me to replace placeholders or fill in a template.
3. Skip questions already answered. Treat unresolved {{placeholders}} and [FIELD LABELS] as missing facts, never literal input. Do not treat an illustrative example as my facts.
4. Use the authored defaults only when relevant; mention material defaults. Ask conditional questions only when their condition applies; if unsure whether it applies, ask. Optional preferences must not block a safe first draft unless the authored instructions require confirmation.
5. Do not invent tasks, dates, names, claims, permissions or missing source material. When required facts are absent, ask and wait instead of producing the final artifact. If everything needed is already supplied, proceed without re-asking.
6. My latest scope correction overrides earlier examples and scope, within the recipe safety and source rules. Resolve conflicts before acting. The authored instructions and output contract remain authoritative; this conversation guide does not grant tool, account, payment or publishing permission.
7. Keep my private answers and generated result in this assistant chat. Do not send them to LazyCoder. Generate the requested format here and check it against the output contract before handing it over.

### Questions to ask only when missing
- What should I use for “The occasion”? [conditional] What it's for and who it's for, the date, and the start and end time. When: A real event date is required for a countdown on calendar dates; the authored fallback uses relative days and must disclose that missing date.
- What should I use for “Guests”? [optional] How many adults and children, and any diets or allergies you already know about.
- What should I use for “Budget”? [optional] The total you want to spend, with the currency, and anything it doesn't need to cover.
- What should I use for “Where it is”? [optional] Home, garden, hall, park or restaurant, and any limits (no oven, out by 18:00, no candles). Authored default: at home, indoors
- What should I use for “Who can help”? [optional] The people who can help, and when they are free. Authored default: the host plus one helper
- What should I use for “Theme and wishes”? [optional] Optional. A theme, the feel you want, activities, music or anything you've already booked. Authored default: relaxed, no set theme
- What should I use for “How guests reply”? [optional] Optional. The name and number or email guests reply to. Leave it blank and the invitation asks them to reply to the message.
- What should I use for “Tone”? [optional] How the invitation and the plan should read. Authored default: warm and friendly Choices: warm and friendly; fun and playful; formal

## LazyCoder delivery guide (delivery-guide-v1)
1. Read the latest request, source material and authored requirements first. Ask only for missing facts. Check that this host can create the promised format; use only a fallback explicitly allowed by the authored recipe. If neither is available, explain the gap before starting. Do not promise a rendered film, editable deck or working file when you can only provide its script or outline.
2. Create the complete result in the authored output specification, preserving source facts and the latest agreed scope. Keep assumptions and missing information explicit. Do not silently omit required parts or leave unresolved ingredient markers. Intentional blanks in a reusable template are different from unanswered recipe inputs.
3. Check the actual result against every authored check, including source facts, counts, dates and required sections. Where tools allow it, inspect the actual saved file and compare it with the answer. Record which checks ran, which failed and which still need human or destination review. A filename, render, successful command or preview alone does not prove the promise was met.
4. Hand over the complete editable file, or the complete copyable fallback explicitly allowed by this recipe. Say which delivery you used and any unresolved limitations. Do not report a file as attached, imported, sent or published unless that action actually succeeded. Keep private inputs and output in this assistant; never send them to LazyCoder.
Use existing authorization for ordinary work. Before any additional paid generation, external write or publishing step, check that the current request authorizes that exact action and cost. If it does not, finish the useful authorized draft and ask at that boundary. Never silently retry or replace an ambiguous paid job.
The authored recipe and latest safe scope remain authoritative. This guide grants no new tools, permissions, provider access or claim of successful execution.

## Authored skill instructions
## 1. Outcome
Plan the party below from now to the end of the clean-up, in the sections set out in part 6: a countdown of tasks on real dates, guest handling, the menu and drinks with amounts, one shopping list, the budget, helper roles, a timed run sheet for the day and backup plans. Done means: every task has a date or a time and a person; every guest is fed and has something to drink, with their diets covered; the costs add up and stay within the budget, or say exactly what to cut; and the host can follow the plan without asking anything else.

## 2. Context
The occasion, date and time: [THE OCCASION, DATE AND TIME]
Guests: [GUESTS]
Budget: [BUDGET]
Where it is: at home, indoors
Who can help: the host plus one helper
Theme and wishes: relaxed, no set theme
How guests reply: [HOW GUESTS REPLY]
Tone: warm and friendly

Who it's for: the person hosting, who wants a calm day where nothing is forgotten, and who may hand parts of the plan to helpers. Write the invitation in this tone: warm and friendly. Write the plan in short, plain lines a helper can follow at a glance.

Blank fill-ins: a value above that still reads as a capitalised placeholder in square brackets (such as [GUESTS]) was left blank.
- No occasion: plan "a relaxed get-together" and say "Occasion not given, please confirm" in the header.
- No date: plan by days before the party ("6 weeks before") with no calendar dates, and say "No date given; add one to get real dates" in the header. No start or end time: assume 3 hours from 14:00, flagged.
- No guest count: plan for 20 adults, flagged in the header.
- No budget: give a modest plan and its estimated total, flagged in the header, and write "None" under the cut list.
- No reply contact: the invitation says "Please reply to this message by <RSVP date>", with no placeholder for a name or number.
- Today's date: if you know it, start the countdown from today. If you don't, start it 6 weeks before the party and add "If the party is sooner, do the overdue tasks first, in this order."

## 3. What to pull out
- The occasion and who it honours, the date, the start and end times, and the setup and pack-down time the venue allows.
- The guests: adults, children with ages, known diets and allergies.
- The budget, its currency, and what it already excludes.
- The helpers and when they are free.
- Anything already booked or decided, which the plan keeps as given.

Edge cases:
- Short notice (under 2 weeks): compress the countdown, keep only what fits, and list what was skipped or simplified ("bought cake instead of ordered") in the header.
- A very small party (under 8): keep the helper table to the people given (one row each), a single shop, and a run sheet in fewer rows.
- A large party (over 60): suggest outside catering or a shared dish plan, hire for tableware, and at least one helper per 20 guests, flagged if there aren't enough.
- Outdoors or in a season that may bring rain, heat or cold: the backup plan names the indoor or covered option and the point at which to decide.
- Children: an adult in charge of children at all times, named in the run sheet, and no small choking-size food for under-4s (whole grapes, whole nuts, popcorn).
- A known allergy: keep the allergen out of shared dishes, label every dish, and name who keeps the allergic guest's medicine.
- Alcohol: a non-alcoholic choice for at least a third of the drinks, food served while alcohol is out, and no alcohol where children are the guests unless the host says so.
- A budget too small for the guest count: say so plainly with the shortfall, then give the cheapest plan that still feeds everyone.
- Something already booked: keep its times exactly and plan around them.

## 4. Steps
1. Fix the frame: the date and times, the venue's access hours, the guest numbers, the budget and the helpers.
2. Work backwards from the party date: the things with the longest lead time first (venue, entertainer, cake order, hire items, invitations), then the RSVP deadline and final-headcount date, then the shopping, then the day before.
3. Choose the menu and drinks for the time of day and the guests' diets, and work out the amounts with the per-head guide in part 5.
4. Build one shopping list from the menu, decor and supplies, and price it. Include small consumables used by preparation, labels, serving and clean-up. Anything already owned must be stated explicitly as an assumption to confirm, with its quantity and use; do not silently assume extra supplies.
5. Check the total against the budget; if it is over, apply the cut list until it fits.
6. Assign the helper roles, then build the run sheet for the day: from setup start to the end of clean-up, with a host-ready time 30 minutes before guests arrive.
7. Any task the countdown leaves for the day itself goes into the run sheet's setup, and the setup start moves earlier by its length.
8. Write the backup plans, then the output, then run the self-check.

## 5. Rules
- Per-head guide (round up, and add 10% to food):
  - Savoury food: 10–12 bites per adult when the party covers a meal time, 6–8 when it doesn't; children about two thirds of that. A sit-down meal is one main portion each plus sides.
  - Cake or dessert: one portion per guest plus 10%.
  - Soft drinks and water: about 3 drinks (250 ml each) per guest for the first 2 hours, then 1 per hour, with water always out.
  - Alcohol, if served: about 1 drink per drinking adult per hour.
  - Ice: about 0.5 kg per guest, double outdoors or in hot weather.
  - Plates and napkins: 1.5 per guest; cups: 2 per guest.
- Every dish is marked with its diets and main allergens: V (vegetarian), VG (vegan), GF (gluten-free), and "contains: <allergen>".
- Before the final-headcount date, buy only things that keep and don't depend on exact numbers: decor, candles, tableware and supplies for the number invited. Cupboard food and drinks are bought after the final-headcount date, for the confirmed number; fresh food 1–2 days before the party.
- Keep a buffer of 10% of the budget unspent for last-minute needs.
- With 3 or more helpers, no shift lasts more than 2 hours. With fewer, mark every task only one person can do "(depends on <name>)".
- Between run-sheet segments, leave a buffer of 10–15 minutes, shown as its own "Buffer" row. Rows otherwise follow on with no gaps. Fit the activities around these buffers and the given event/access times; shorten optional activities if necessary, never a buffer. A backup plan must preserve the same buffers, access hours and people's availability. For a helper dropping out, state the revised tasks and exact times or simplify the activity; do not tell the host to skip a buffer.
- Derive all timing explanations from the final run sheet. For any stated event-window buffer total, list only Buffer rows wholly inside the event start/end and add their minutes. A post-event buffer belongs to clean-up, not to the event. Activity minutes plus in-event buffer minutes must equal the event duration. Do not invent a timing conflict if that arithmetic fits.
- Prices are estimates only, in the budget's currency. Never present one as a real quote. Use only the bookings and names given; never invent a supplier, a phone number or a booking.
- Write every date with its weekday, as in "Sat 12 Dec 2026", and times as 24-hour hh:mm.

## 6. Output
Use these sections in this order. Write "None" under any that is empty.
1. Plan header: the occasion, date, start and end time, venue and access hours, guests (adults, children, diets), budget, helpers, and every assumption and skipped item.
2. Countdown: a table with the columns Date | Days to go | Task | Who | Done when, in date order, from the start of planning to the day before. Long-lead items carry "(book early)". Overdue tasks, if any, come first, marked "(do now)".
3. Guests: the date to send invitations, the RSVP deadline, the date to chase anyone who hasn't replied, and the final-headcount date (at least 5 days before, or 2 days for short notice). Then a ready-to-send invitation of at most 60 words: what, who for, date, time, place, RSVP by, how to reply (the reply contact above, or "reply to this message"), and a line asking about diets and allergies. No placeholders.
4. Menu and drinks: a table with the columns Item | Per head | Total | Diets and allergens | Made or bought, with one row per dish and drink.
5. Shopping list, grouped in this order: Fresh food; Cupboard food; Drinks and ice; Tableware and supplies; Decor and party items; Other. Under each, a table with the columns Item | Quantity | Estimated cost | Buy by | Cut first?, where Cut first? is "Yes" for items the party can do without.
6. Budget: a table with the columns Category | Estimate | Share of budget, then the 10% buffer, the total, and one line: "Within budget by <amount>" or "Over budget by <amount>". Then "Cut first, in order": up to 5 cuts, each with what it saves.
7. Helpers: a table with the columns Role | Who | From–to | Duties. Mark any task only one person can do "(depends on <name>)".
8. Run sheet for the day: a table with the columns From–to | Minutes | What happens | Who | Cue to start | Done when, from setup start to the end of clean-up and handing back the venue. Every row has a from–to time and its length in minutes, setup and clean-up included (split them into a few rows, such as tables and decor, food out, rubbish and hand-back). Include the host-ready time as its own row, every activity, music or speech with its duration, the food going out, the cake, and the clean-up.
9. Backup plans: a table with the columns Risk | Early sign | What to do | Get ready in advance, covering at least: weather (if any part is outdoors), more or fewer guests than expected, food or drink running short, a helper dropping out, and an allergic reaction (who holds the medicine, and call emergency services).
10. Safety and access: 3–6 lines specific to this party, such as children's supervision, allergens, alcohol, candles and heat, step-free access and toilets.

## 7. Self-check
Before replying, check each of these and fix any failure:
- Every countdown task has a date (or days before), a person and a done test, and the dates are in order and before the party.
- The final-headcount date comes before the fresh-food shopping and any order that needs numbers.
- The run sheet covers setup start to the end of clean-up; each row starts when the one before ends, with buffers as their own 10–15 minute rows; every row has a from–to time, its minutes and a person; there is a host-ready row; and every row falls within the venue's access hours.
- Nothing that depends on numbers (cupboard food, drinks, fresh food, orders by headcount) is bought before the final-headcount date.
- The invitation has no placeholders.
- Every guest has food and drink in the menu totals, and every diet and allergy in the inputs is covered by at least one dish that is safe for them.
- Every menu item and every consumable used in preparation, labels, serving, countdown, run sheet or backups is accounted for: either on the priced shopping list, or in an explicit already-owned assumption to confirm with quantity and use. "Bought ready" still needs a priced shopping entry. Every shopping item is used somewhere.
- The budget total equals the sum of its lines plus the buffer, and the over or under line is right.
- Every backup plan names an action, not only the risk, and preserves buffers and access hours. Check a helper-dropout plan against the remaining person's available time. Recount any buffer totals or activity-day statements in prose from the final tables; fix contradictions before replying.
Then reply with the output only, ending with one line: "Checked: <n> countdown tasks, <n> run-sheet rows, <n> items to buy, total <amount> of <budget>."

## 8. Setup
Works as one paste in any chat app, with no tools or plugins. Prices are estimates from general knowledge, so check them before you buy. If the guest list or a booking confirmation is a file, you can attach it and write "see attached" in that box.

Paste the result after your assistant creates it. This optional check stays in this tab and is not sent to LazyCoder.