What problem does it solve? Choosing an event date is the decision every other plan hangs off, yet organizers routinely pick a day type that fights their audience's calendar, fix one date before talking to venues, or announce before payment handling exists. This Skill structures the date decision so conflicts, observances, and announcement timing are checked deliberately instead of discovered after publication. ## Core Features & Use Cases - Day-type decision from audience time ownership: Weekday for working professionals on employer time (DevOpsDays guide), weekend for students and hobbyists (MLH guide), with explicit handling of mixed audiences instead of a compromise slot. - Layered constraint checks: Audience-calendar pass, competing-event scan with dodge-or-piggyback calls, and multi-geography observance verification, with every category recorded as checked or outstanding rather than assumed clear. - Candidate windows and announcement gating: Carries three to five surviving windows into venue negotiation ("Get Options") and blocks any announcement until money handling exists. - Use Case: A team planning a two-day conference for working engineers across three countries gets a weekday recommendation with its source, verified holiday checks per country, four candidate windows for the venue, and an announcement plan gated on ticketing being ready. ## Quick Start Ask the assistant to help pick a date for your technical conference or hackathon, describing the audience, location, and any fixed constraints.
