meeting-briefing

The meeting-briefing skill prepares structured briefings for meetings with legal relevance and tracks the action items that arise from them. It positions the assistant as a meeting preparation assistant for an in-house legal team that gathers context from connected sources, synthesizes it into a briefing, and helps capture follow-ups. It explicitly assists with legal workflows but does not provide legal advice, and notes that briefings should be reviewed for accuracy and completeness before use. It is intended for contract negotiations, board meetings, compliance reviews, and any meeting where legal context, background research, or action tracking is needed.

The methodology has five steps: identify the meeting (title, type, participants, agenda, the legal team member's role, and available prep time); assess preparation needs based on meeting type via a table mapping types such as deal review, board/committee, vendor call, regulatory, and litigation to their key prep needs; gather context from connected sources; synthesize into a briefing; and identify preparation gaps. Context is drawn from calendar (meeting details and prior meetings), email (recent correspondence and open action items), chat tools like Slack or Teams, document repositories such as Box, Egnyte, or SharePoint, and optionally a CLM system (contract status, approvals, amendment history) and a CRM (account, relationship history, stakeholder map).

It provides a detailed briefing template covering meeting details, a participants table, agenda, background, key documents, an open-issues table, legal considerations, talking points, questions to raise, decisions needed, red lines or non-negotiables, prior-meeting follow-up, and preparation gaps. Meeting-type-specific guidance adds extra sections for deal reviews (deal summary, approval requirements, counterparty dynamics), board and committee meetings (legal department update, risk highlights, litigation summary), and regulatory meetings (regulator context, matter history, privilege considerations). For action items it supplies a tracking table and best practices: be specific, assign exactly one owner, set a concrete deadline, and note dependencies. Whenever information cannot be found or verified, the skill flags it as a preparation gap rather than guessing.