borghei/Claude-Skills / legal/legal-meeting-briefing
legal-meeting-briefing
VerifiedPrepare structured briefings for meetings with legal relevance and track action items. Use when prepping legal meetings.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| references/briefing_templates.md | markdown | 11.0 KB |
| references/meeting_type_guides.md | markdown | 12.9 KB |
| scripts/action_item_tracker.py | script | 15.2 KB |
| scripts/meeting_brief_generator.py | script | 16.2 KB |
references/briefing_templates.md
View on GitHub# Meeting Briefing Templates
Complete 13-section briefing template, action item tracking template, and best practices.
## Table of Contents
- [Standard Briefing Template](#standard-briefing-template)
- [Section Details](#section-details)
- [Action Item Tracking](#action-item-tracking)
- [Best Practices](#best-practices)
- [Distribution and Security](#distribution-and-security)
## Standard Briefing Template
The standard briefing contains 13 sections. Not all sections are required for every meeting; select sections based on meeting type and relevance.
| # | Section | Required | Purpose |
|---|---------|----------|---------|
| 1 | Meeting Details | Always | Date, time, location, type, preparer |
| 2 | Participants | Always | Who is attending with roles and interests |
| 3 | Agenda / Expected Topics | Always | What will be discussed |
| 4 | Background and Context | Always | Relevant history and context |
| 5 | Key Documents | When applicable | Documents to review or reference |
| 6 | Open Issues | When applicable | Unresolved items with status and owners |
| 7 | Legal Considerations | Always | Legal risks, compliance, or regulatory concerns |
| 8 | Talking Points | When presenting | Key messages with supporting context |
| 9 | Questions to Raise | When information-gathering | Questions with "why this matters" context |
| 10 | Decisions Needed | When action required | Decision options with recommendations |
| 11 | Red Lines / Non-Negotiables | For negotiations | Positions that cannot be conceded |
| 12 | Prior Meeting Follow-Up | When recurring | Action items from previous meeting |
| 13 | Preparation Gaps | Always | Missing information or unresolved prep items |
## Section Details
### Section 1: Meeting Details
```markdown
| Field | Detail |
|-------|--------|
| Title | [Meeting title] |
| Type | [Deal Review / Board / Vendor / etc.] |
| Date | [YYYY-MM-DD] |
| Time | [HH:MM - HH:MM TZ] |
| Location | [Room / Video link] |
| Duration | [XX minutes] |
| Prepared by | [Name, Title] |
| Prepared on | [YYYY-MM-DD] |
| Distribution | [Confidential / Internal / Restricted] |
```
### Section 2: Participants
```markdown
| Name | Organization | Role | Key Interests |
|------|-------------|------|---------------|
| [Full name] | [Company/Dept] | [Title/Role in meeting] | [What they care about] |
```
**Participant Notes:**
- Include all confirmed attendees plus expected attendees
- Note decision-makers vs. observers
- For external participants, include brief background
- Note any participants who declined or are tentative
### Section 3: Agenda / Expected Topics
```markdown
1. [Topic] (XX min) - [Presenter/Lead]
2. [Topic] (XX min) - [Presenter/Lead]
3. [Topic] (XX min) - [Presenter/Lead]
4. Open discussion (XX min)
```
**Agenda Notes:**
- Allocate time per topic
- Identify who leads each topic
- Place most important items first (attention is highest early)
- Reserve time for open discussion and next steps
### Section 4: Background and Context
Provide 2-3 paragraphs of relevant background:
- What led to this meeting
- Key events since the last meeting on this topic
- External developments that affect the discussion
- Brief history for new participants
### Section 5: Key Documents
```markdown
| # | Document | Version | Status | Location | Required Reading |
|---|----------|---------|--------|----------|-----------------|
| 1 | [Name] | [v#] | [Draft/Final] | [Link] | [Yes/Optional] |
```
### Section 6: Open Issues
```markdown
| # | Issue | Status | Owner | Priority | Target Date |
|---|-------|--------|-------|----------|-------------|
| 1 | [Description] | [Open/In Progress/Blocked] | [Name] | [H/M/L] | [Date] |
```
**Issue Status Definitions:**
- **Open**: Not yet started
- **In Progress**: Actively being worked
- **Blocked**: Cannot proceed; dependency or decision needed
- **Resolved**: Completed since last meeting (include for context)
### Section 7: Legal Considerations
Structure legal considerations as:
```markdown
### Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [Risk] | [H/M/L] | [H/M/L] | [Mitigation strategy] |
### Compliance Considerations
- [Applicable regulation and requirement]
### Privilege Notes
- [What is privileged and should not be shared outside legal]
```
### Section 8: Talking Points
```markdown
1. **[Topic/Message]**
- Supporting context: [Facts, data, or precedent]
- Key message: [What to communicate]
- If challenged: [Fallback position or additional support]
2. **[Topic/Message]**
- Supporting context: [Facts, data, or precedent]
- Key message: [What to communicate]
- If challenged: [Fallback position or additional support]
```
**Talking Points Guidelines:**
- Lead with the conclusion or recommendation
- Support with 2-3 facts or data points
- Anticipate pushback and prepare responses
- Keep each point to 2-3 sentences when spoken
### Section 9: Questions to Raise
```markdown
1. **[Question]**
- *Why this matters:* [Business/legal impact of the answer]
- *Desired outcome:* [What you hope to learn or achieve]
- *If answer is X:* [Next step if answered one way]
- *If answer is Y:* [Next step if answered another way]
```
### Section 10: Decisions Needed
```markdown
| # | Decision | Options | Recommendation | Rationale | Deadline |
|---|----------|---------|----------------|-----------|----------|
| 1 | [What needs to be decided] | A: [Option]\nB: [Option] | [Which option and why] | [Key reasoning] | [By when] |
```
**Decision Framework:**
- Present no more than 3 options per decision
- Always include a recommendation with rationale
- Note consequences of delayed decision
- Identify who has authority to decide
### Section 11: Red Lines / Non-Negotiables
For negotiation meetings only:
```markdown
| # | Position | Rationale | If Challenged |
|---|----------|-----------|---------------|
| 1 | [Non-negotiable term] | [Why this cannot be conceded] | [Response to pushback] |
```
**Red Line Guidelines:**
- Keep to 3-5 items maximum (everything else is negotiable)
- Distinguish between true red lines and strong preferences
- Pre-align with business stakeholders
- Never reveal red lines to counterparties
### Section 12: Prior Meeting Follow-Up
```markdown
| # | Action Item | Owner | Original Deadline | Status | Notes |
|---|------------|-------|------------------|--------|-------|
| 1 | [Action from prior meeting] | [Name] | [Date] | [Complete/In Progress/Overdue] | [Brief update] |
```
### Section 13: Preparation Gaps
```markdown
| # | Gap | Impact if Unresolved | Action Needed | Owner | Deadline |
|---|-----|---------------------|---------------|-------|----------|
| 1 | [What is missing] | [How it affects the meeting] | [Steps to resolve] | [Name] | [Date] |
```
## Action Item Tracking
### Action Item Template
```markdown
| # | Action | Owner | Priority | Deadline | Meeting Source | Status |
|---|--------|-------|----------|----------|---------------|--------|
| 1 | [Specific, actionable task] | [Single name] | [H/M/L] | [YYYY-MM-DD] | [Meeting title] | [Open] |
```
### Action Item Standards
| Principle | Requirement | Bad Example | Good Example |
|-----------|-------------|-------------|-------------|
| Specific | Describe exactly what must be done | "Handle the NDA" | "Draft mutual NDA for Acme Corp review" |
| Single owner | One person accountable | "Legal team" | "Jane Smith" |
| Specific date | Calendar date, not relative | "Soon" or "ASAP" | "2026-04-20" |
| Measurable | Clear completion criteria | "Work on contract" | "Finalize and send redline of Section 5" |
| Dependencies noted | Call out blockers | (none) | "Blocked by: finance approval of budget" |
### Priority Definitions
| Priority | Definition | Examples |
|----------|-----------|---------|
| High | Deadline within 7 days or blocking other work; legal/regulatory deadline | Court filing, regulatory response, deal closing |
| Medium | Deadline within 30 days; important but not immediately blocking | Contract review, policy update, vendor assessment |
| Low | Deadline beyond 30 days; enhancement or non-urgent improvement | Process improvement, template update, training |
### Follow-Up Cadence
| Priority | Check-In Frequency | Escalation Trigger | Escalation To |
|----------|-------------------|-------------------|---------------|
| High | Daily | 2 consecutive missed check-ins | Supervisor + meeting owner |
| Medium | Weekly | 1 missed weekly check-in | Meeting owner |
| Low | Monthly | 1 missed monthly check-in | Meeting owner |
| Overdue (any) | Immediate escalation | Any item past deadline | Supervisor + meeting owner |
### Status Definitions
| Status | Meaning | Next Action |
|--------|---------|-------------|
| Open | Not yet started | Confirm owner and timeline |
| In Progress | Actively being worked | Monitor per follow-up cadence |
| Blocked | Cannot proceed; awaiting dependency | Escalate to remove blocker |
| Complete | Done; deliverable available | Archive and confirm with requester |
| Overdue | Past deadline and not complete | Immediate escalation; new deadline |
## Best Practices
### Briefing Preparation
| Practice | Timing | Detail |
|----------|--------|--------|
| Start early | 3-5 days before | Begin gathering information; identify gaps early |
| Draft and circulate | 2-3 days before | Share draft for input from key participants |
| Finalize | 1 day before | Incorporate feedback; distribute final version |
| Pre-brief | 30 min before | Quick alignment with key allies or decision-makers |
| Post-meeting | Within 2 hours | Capture action items; distribute summary |
### Common Mistakes to Avoid
| Mistake | Impact | Better Approach |
|---------|--------|-----------------|
| Too long | Not read; key points buried | Keep to 3-5 pages; use appendix for details |
| Too late | No time to prepare or give input | Distribute 2+ days before meeting |
| Missing "so what" | Facts without analysis or recommendation | Always include recommendation and rationale |
| No follow-up | Action items lost; commitments forgotten | Capture items within 2 hours; start follow-up cadence |
| Wrong audience | Confidential info shared; irrelevant to attendees | Check distribution list; mark privilege appropriately |
## Distribution and Security
### Distribution Classifications
| Classification | Who Receives | Handling |
|---------------|-------------|----------|
| Privileged and Confidential | Named recipients only | Mark each page; do not forward without counsel approval |
| Confidential | Internal team and approved participants | Do not share externally; reference company confidentiality policy |
| Internal | All meeting participants | Share freely within organization |
| Restricted | Board/committee members only | Board portal distribution; no copies |
### Retention
| Document Type | Retention Period | After Retention |
|--------------|-----------------|-----------------|
| Board briefings | Per corporate governance policy (typically 7 years) | Secure destruction |
| Litigation briefings | Duration of matter + 3 years | Secure destruction |
| Routine meeting briefings | 1 year | Secure destruction |
| Action item records | Until completion + 1 year | Archive |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |