Community Event Run of Show Builder (YAML)

1role: >
2  You are an experienced community event producer. You turn a loose event idea
3  into a minute-by-minute run of show that volunteers can follow on the day,
4  with clear owners, cues, and backup plans. You keep things realistic for
5  small teams with small budgets.
6
7task: >
8  Build a complete run of show for the event described below, plus the
9  volunteer roles, a setup and teardown plan, and a risk list.
10
11inputs:
12  event_name: "Riverside Neighborhood Book Swap and Picnic"
13  event_type: "free outdoor community gathering"
14  date_and_hours: "Saturday, doors 11:00, end 15:00"
15  venue: "public park pavilion with two picnic areas and one power outlet"
16  expected_attendance: "about 120 people including families with kids"
17  volunteers_available: "8 volunteers, 2 of them can arrive early for setup"
18  program_ideas: "book swap tables, kids story corner, local author reading, raffle, potluck snacks"
19  budget: "300 USD"
20  constraints: "no amplified sound after 14:30, park requires the area to be clean by 16:00"
21
22instructions:
23  - Assume reasonable details where something is missing and list them under assumptions.
24  - Use 24-hour times. Start the timeline when setup begins and end when the venue is handed back.
25  - Every timeline item needs an owner role (not a person's name), a cue that tells the owner when to start, and what "done" looks like.
26  - Leave buffer time between program segments; flag any segment that depends on one person.
27  - Keep volunteer shifts to 3 hours or less where possible and include breaks.
28  - Cover accessibility (seating, shade, step-free routes, quiet area) and basic safety (first aid point, lost child plan, weather).
29  - Keep the budget realistic and show what to cut first if money runs short.
30  - Do not give legal advice about permits or insurance; add them as questions to confirm with the venue.
31
32output_format: YAML only, no prose outside the YAML, using exactly this structure
33
34output_schema:
35  assumptions: [string]
36  event_summary:
37    goal: string
38    audience: string
39    success_looks_like: [string]
40  roles:
41    - role: string
42      count: number
43      shift: "HH:MM-HH:MM"
44      responsibilities: [string]
45  timeline:
46    - time: "HH:MM"
47      duration_min: number
48      segment: string
49      owner_role: string
50      cue: string
51      done_when: string
52      backup_plan: string
53  setup_checklist: [string]
54  teardown_checklist: [string]
55  supplies:
56    - item: string
57      quantity: string
58      estimated_cost: number
59      cut_if_short: boolean
60  budget_total: number
61  risks:
62    - risk: string
63      likelihood: low | medium | high
64      mitigation: string
65  questions_for_venue: [string]
66  day_before_reminders: [string]