meeting-briefing

name	meeting-briefing
description	Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.

Meeting Briefing Skill

Prepare structured briefings for meetings with legal relevance and track resulting action items.

Important: You assist with legal workflows but do not provide legal advice. Meeting briefings should be reviewed for accuracy and completeness before use.

Meeting Prep Methodology

Step 1: Identify the Meeting

• Meeting title and type: Deal review, board meeting, vendor call, team sync, client meeting, regulatory discussion
• Participants: Roles and interests
• Agenda: Formal agenda or expected topics
• Your role: Advisor, presenter, observer, negotiator

Step 2: Assess Preparation Needs

Meeting Type	Key Prep Needs
Deal Review	Contract status, open issues, counterparty history, negotiation strategy
Board / Committee	Legal updates, risk register highlights, pending matters, regulatory developments
Vendor Call	Agreement status, open issues, performance metrics, negotiation objectives
Regulatory / Government	Matter background, compliance status, prior communications, counsel briefing
Litigation / Dispute	Case status, recent developments, strategy, settlement parameters

Step 3: Gather Context from Connected Sources

• Calendar: Meeting details, prior meetings with same participants
• Email: Recent correspondence, prior follow-ups, open action items
• Chat: Recent discussions, team decisions
• Documents: Agendas, prior meeting notes, relevant agreements
• CLM: Relevant contracts, negotiation status
• CRM: Account information, relationship history

Step 4: Synthesize into Briefing

## Meeting Brief

### Meeting Details
- **Meeting**: [title]
- **Date/Time**: [date and time]
- **Your Role**: [advisor / presenter / negotiator / observer]

### Participants
| Name | Organization | Role | Key Interests |
|---|---|---|---|
| [name] | [org] | [role] | [what they care about] |

### Background and Context
[2-3 paragraph summary]

### Open Issues
| Issue | Status | Owner | Priority |
|---|---|---|---|
| [issue] | [status] | [who] | [H/M/L] |

### Legal Considerations
[Specific legal issues, risks, or considerations]

### Talking Points
1. [Key point with supporting context]

### Decisions Needed
- [Decision] -- [options and recommendation]

### Red Lines / Non-Negotiables
[If negotiation: positions that cannot be conceded]

Action Item Tracking

## Action Items from [Meeting Name] -- [Date]

| # | Action Item | Owner | Deadline | Priority | Status |
|---|---|---|---|---|---|
| 1 | [specific task] | [name] | [date] | [H/M/L] | Open |

Best Practices

• Be specific: "Send redline of Section 4.2" not "Follow up on contract"
• Assign an owner: Exactly one person per action item
• Set a deadline: Specific date, not "soon" or "ASAP"
• Distinguish types: Legal team actions, business team actions, external actions, follow-up meetings