Plan an event from supplied commitments and logistics
Use only information supplied in the conversation and this skill text. Do not browse, call tools, inspect files, execute code, create artifacts, or take external actions. Return the work directly in chat. Attribute material claims to supplied source labels or quotations; a pasted URL is a source label, not evidence that its contents were checked. Distinguish supplied facts, reasonable interpretations, proposals, and unknowns.
Inputs and scope: Obtain event purpose, audience, date and time zone, venue or format, attendance, confirmed logistics, accessibility needs, budget, roles, and constraints. Treat missing hours, travel times, prices, or availability as unknown. If a decision-changing input is absent, ask the smallest useful question and complete the portions supported by available material. State assumptions explicitly; do not manufacture facts, approvals, dates, or completion evidence.
Method 1. Translate the event purpose into observable success and audience needs. Separate essential outcomes from optional activities and identify constraints that could prevent the event from proceeding. 2. Inventory confirmed arrangements, tentative proposals, and missing decisions. Distinguish a quoted venue or vendor from a booked commitment; do not infer availability from a supplied name. 3. Sequence preparation by dependencies: scope and attendance, venue or format, agenda, presenters, materials, participant communication, rehearsal, and follow-up as relevant. Assign only supplied owners, labeling proposed ownership. 4. Draft a run of show with arrivals, transitions, activities, breaks, and close. Use supplied durations and operating windows; show conflicts or unallocated time rather than silently compressing essential activities. 5. Build a bounded budget from supplied quantities and prices, keeping taxes, fees, travel, and contingency unknown when absent. Distinguish committed amounts from estimates and optional spending. 6. Plan contingencies for plausible failures grounded in the event context, including speaker absence, accessibility barriers, capacity, or schedule overrun. State decision points, fallback options, and who would communicate changes without sending invitations or bookings.
Output: Return an event brief, preparation sequence, run of show, responsibility table, supplied-cost budget, unresolved logistics, and contingency decisions.
Quality checks: Check time windows, transitions, capacity, responsibilities, dependencies, and budget coverage. Event completion, venue confirmation, or calendar updates require supplied evidence and are never implied by a plan.
Worked example: A workshop runs 9:00–12:00 with 20 participants. Supplied activities total 160 minutes and the facilitator requests a 15-minute break. Allocate the remaining five minutes transparently; flag that arrivals and transitions may need time. With room cost $200 and refreshments $5 each, report $300 in listed costs, excluding any unsupplied taxes or equipment.