icaire-events-lead-prepare-event-brief
Prepare ICAIRE briefing packs for events and visits. Use when creating agendas, attendee lists, purpose notes, speaker notes, logistics summaries, risk notes, or follow-up plans.
SKILL.mdskills/icaire-events-lead-prepare-event-brief/SKILL.md
GitHubICAIRE Events Lead: Prepare Event Brief
Use this skill to prepare a practical briefing pack for an ICAIRE event, visit, workshop, or partner session.
Contract
- Start from the event or visit, audience for the brief, date, host, purpose, and decisions or actions the brief must support.
- Use BigBrain or the ICAIRE MCP connector for ICAIRE facts, prior meetings, attendees, partner context, initiatives, commitments, and open follow-ups when the user has not supplied enough source material.
- Produce an operationally useful pack: agenda, attendee context, speaker notes, logistics, risks, and follow-up plan.
- Separate confirmed logistics from placeholders, assumptions, and unresolved planning questions.
- Tune detail to the use case: leadership prep, staff run-of-show, external partner briefing, or post-event follow-up planning.
Workflow
- Identify the event type, date, venue or platform, host, attendees, audience for the brief, and desired outcome.
- Gather provided materials such as agenda drafts, invite lists, bios, meeting notes, logistics, and partner context.
- Retrieve ICAIRE context from BigBrain or the ICAIRE MCP when attendee relationships, prior commitments, initiative links, or sensitivities are unclear.
- Build the brief sections: purpose, agenda, attendee list, roles, preparation notes, speaker notes, logistics, risks, and follow-up plan.
- Highlight decision points, protocol considerations, missing materials, and owner-specific actions.
- Add a post-event follow-up plan with likely recap, thank-you, action item, and memory-ingest needs.
- Verify that attendee names, roles, agenda times, logistics, and risks are grounded in source material or clearly marked as unresolved.
Guardrails
- Do not invent attendees, timings, venues, logistics, speaker roles, security needs, or protocol requirements.
- Do not flatten real risks into generic "watch items"; make operational, reputational, protocol, and follow-up risks visible.
- Do not write a public event description when the user needs an internal run sheet or leadership prep brief.
- Do not expose internal notes in partner-facing material unless the user asks for an external version.
- Do not update durable memory unless the user explicitly asks for ingestion or persistence.
Output Expectations
Return a briefing pack or run-of-show structure. When useful, include:
- event purpose
- agenda
- attendee list and roles
- speaker notes or talking points
- logistics
- risks and mitigations
- protocol or sensitivity notes
- owner checklist
- follow-up plan
- assumptions and missing information