icaire-chief-of-staff-prepare-brief

Prepare concise ICAIRE leadership briefs before meetings, decisions, or follow-ups. Use when creating context briefs, decision memos, recommended positions, follow-up asks, or meeting prep notes for l

SKILL.md

GitHub

ICAIRE Chief Of Staff: Prepare Brief

Use this skill to prepare a concise leadership brief that helps ICAIRE leaders walk into a meeting, decision, or follow-up with context, options, and clear asks.

Contract

  • Start with the leadership moment: meeting, decision, follow-up, partner conversation, or internal alignment.
  • Use BigBrain or the ICAIRE MCP connector for ICAIRE facts, people, meetings, initiatives, and relationship context when the user has not supplied enough source material.
  • Keep the brief short enough to be read quickly, while making decisions, sensitivities, and follow-up asks explicit.
  • Separate recommended position from evidence, assumptions, and open questions.
  • Match tone to the audience and sensitivity of the situation.

Workflow

  1. Identify the leader, audience, meeting or decision context, deadline, and desired outcome.
  2. Gather provided material and retrieve current ICAIRE context if people, organizations, prior meetings, initiatives, or decisions are unclear.
  3. Summarize the relevant background, recent developments, stakeholder interests, and constraints.
  4. Identify the decision or conversation objective, the recommended position, and the rationale.
  5. Draft specific talking points, questions to ask, risks or sensitivities, and follow-up asks.
  6. Add unresolved questions and missing source material if the brief is not fully supported.
  7. Verify that names, roles, affiliations, prior commitments, and proposed asks are grounded in source material or retrieved ICAIRE context.

Guardrails

  • Do not invent relationship history, commitments, approvals, titles, or institutional positions.
  • Do not write a long research memo when the user asked for leadership prep.
  • Do not flatten sensitivities; highlight where language should be careful.
  • Do not present a recommendation as settled if the evidence is incomplete.
  • Do not persist updates to BigBrain unless the user explicitly asks for memory ingestion or profile updates.

Output Expectations

Return the requested brief in a compact structure. When useful, include:

  • purpose and desired outcome
  • relevant context
  • key facts and recent developments
  • recommended position
  • rationale
  • talking points
  • questions to ask
  • risks or sensitivities
  • follow-up asks
  • missing information or assumptions