aaif/aaif-events

Write the LinkedIn launch/announcement post for an AAIF event when RSVPs open. Use when asked to draft the announcement, launch post, or "RSVPs are open" post for an AAIF event.

Write the pre-event reminder to people who RSVP'd to an AAIF event (sent ~1 week out and the morning of). Use when asked to draft the attendee reminder / "see you tomorrow" note for an AAIF event.

Audit the community Slack workspace and report it as one HTML page — whether every chapter has its public and organizer channels and the right people in them, which subject-matter rooms have gone quiet or overlap, and what the headline member count is actually made of. Use when asked about Slack coverage for chapters, whether organizers are in their channels, who is in an -organizers channel, workspace health, channel clutter, inactive channels or accounts, or the newcomer experience.

Take a versioned local backup of critical AAIF ops data — the Community Intake Ops sheet by default, or any Drive file / local file you name. Snapshots are immutable and timestamped so you keep a full history. Use when asked to back up / snapshot the intake data (or another file) before a risky edit.

Write copy for a 6-slide LinkedIn carousel announcing an AAIF event. Use when asked to draft carousel slides/copy for an AAIF event (built from the LinkedIn Carousel template).

Normalize and fix data quality in the AAIF Community Intake Ops sheet — canonicalize LinkedIn URLs, fix name/city casing & whitespace, derive each person's city from the form's free-text answer (City > Extracted, capital when only a country is given), flag bad/missing emails and duplicates, and surface broken rows in bright red. Reports & proposes by default; only writes on explicit approval. Use when asked to clean up / normalize / fix the intake data.

Write the "AAIF Community Organizer Update" (the Pulse) — the periodic Slack post to organizers recapping recent chapter events, community/foundation news, upcoming events from the Luma calendar, and admin/tooling changes. Use when asked to draft the Pulse, the organizer update, or the community update post.

Create a new AAIF city chapter in the "Chapters" Google Drive by cloning TemplateCity and rebranding all assets. Use when asked to add/launch/set up a new AAIF city, chapter, or location.

Create a new event in an AAIF chapter or online series by cloning the example section in its Event Tracker.docx and stamping all phase task due-dates from the event date; can then create the live Luma event page from the entry (proposal shown first, created only on explicit user approval). Use when asked to add/schedule/set up a new event for a chapter or series, or to put an event on Luma.

Create a new AAIF online event series in the "Online" Google Drive folder by cloning TemplateSeries and rebranding all assets. Use when asked to add/launch/set up a new AAIF online series (reading group, paper club, webinar, online discussion) — not a city chapter.

Turn an event's tracker entry into the slide text for the AAIF "Day of Event" deck. Use when asked to fill/write the day-of slides or event deck for an AAIF event.

Report task status for an AAIF chapter or online series — which event tasks are overdue or due soon, grouped by owner, read from the Event Tracker.docx — plus read-only Luma registration stats (going/waitlist/checked-in counts) for pushed events. Use when asked for the status / health / what's-due / RSVP numbers of a chapter or series' events.

Write the Luma event-page description for an AAIF in-person event. Use when asked to draft the Luma description / event page copy for an AAIF event.

Write the post-event LinkedIn recap for an AAIF event (posted within 48 hours, with photos). Use when asked to draft the recap, thank-you, or wrap-up post after an AAIF event.

Write a speaker bio (a 60-80 word bio + a one-liner) for an AAIF in-person event speaker. Use when asked to draft/write a speaker bio for an AAIF event or chapter.

Write a short, warm speaker-invite DM or email for an AAIF in-person event. Use when asked to draft a speaker invite, outreach DM, or ask-someone-to-speak message for an AAIF event.

Run the whole AAIF estate sync in order — check the intake and the decision queue, then chapters onto the Chapters List with their Drive folders and Slack rooms, then organizers into About docs, CRMs, Drive access and organizer rooms, then every chapter's Luma page and event health, then the Slack topic rooms and workspace. Each phase measures before it proposes and proposes before it writes. Reports by default; writes only on explicit approval. Use when asked to sync the estate, run the sync, sync everything, do the chapter/organizer sync, or bring the sheets, Drive, Slack and Luma back in step.

Sync AAIF chapter organizer badges (SVG + PNG) into each chapter's own Drive folder — generate missing badges for chapters that don't have them yet, and optionally regenerate all of them after a design change. Use when asked to add/sync/update/regenerate chapter organizer badges.

Push accepted intake cities and organizer names onto the public Chapters List sheet — appending a row for a city that has none, merging organizer names into the row that exists — and audit every chapter row's Luma page. Reports and proposes by default; writes only on explicit approval. Use when asked to add a new city to the chapters sheet, update the chapters list, sync chapter rows, check the 100-chapter cap, or find chapters whose Luma link is dead.

Push accepted and pipeline intake people into each chapter's own files — the Organizers list in its About doc, the people rows in its private Attendee CRM, and the per-chapter Drive grants that let its organizers open the folder — plus the Slack ID and Drive Email identity columns. Reports and proposes by default; writes only on explicit approval. Use when asked to sync organizers, update a chapter's About doc, add intake people to a chapter CRM, give an organizer access to their chapter folder, or fix someone whose Slack or Drive address does not match their intake row.

Record where each chapter actually lives — its Drive folder and its public, organizer and country Slack channels — on the Chapters List, then create the rooms that plan names, add accepted organizers to them, and keep each country channel's chapter directory current. Reports and proposes by default; every Slack write needs explicit human approval. Use when asked to map chapters to Slack channels, create or rename a chapter channel, add organizers to their channel, post a country directory, or remove non-organizers from an organizer room.

Triage new AAIF community intake submissions (organizers, hosts/venues, speakers) from the Intake Ops sheet — summarize who's awaiting review, assess fit, and draft next-step outreach. Use when asked to review/triage new applicants, check the intake queue, or produce an intake digest.

Apply a change to an existing AAIF event (chapter or series) — edit detail fields like speakers/venue/capacity, or move the date and recompute all task due-dates, then flag which marketing/banner assets are now stale (speaker, venue/location, platform/join-link, and date changes set flags); can also sync the change to the live Luma event page (diff shown first, pushed only on explicit user approval). Use when asked to update/change/edit an event's details or date.