meeting-briefing-deal-review-meetings
Sub-skill of meeting-briefing: Deal Review Meetings (+2).
Best use case
meeting-briefing-deal-review-meetings is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of meeting-briefing: Deal Review Meetings (+2).
Teams using meeting-briefing-deal-review-meetings should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deal-review-meetings/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How meeting-briefing-deal-review-meetings Compares
| Feature / Agent | meeting-briefing-deal-review-meetings | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of meeting-briefing: Deal Review Meetings (+2).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deal Review Meetings (+2) ## Deal Review Meetings Additional briefing sections: - **Deal summary**: Parties, deal value, structure, timeline - **Contract status**: Where in the review/negotiation process; outstanding issues - **Approval requirements**: What approvals are needed and from whom - **Counterparty dynamics**: Their likely positions, recent communications, relationship temperature - **Comparable deals**: Prior similar transactions and their terms (if available) ## Board and Committee Meetings Additional briefing sections: - **Legal department update**: Summary of matters, wins, new matters, closed matters - **Risk highlights**: Top risks from the risk register with changes since last report - **Regulatory update**: Material regulatory developments affecting the business - **Pending approvals**: Resolutions or approvals needed from the board/committee - **Litigation summary**: Active matters, reserves, settlements, new filings ## Regulatory Meetings Additional briefing sections: - **Regulatory body context**: Which regulator, what division, their current priorities and enforcement patterns - **Matter history**: Prior interactions, submissions, correspondence timeline - **Compliance posture**: Current compliance status on the relevant topics - **Counsel coordination**: Outside counsel involvement, prior advice received - **Privilege considerations**: What can and cannot be discussed; any privilege risks
Related Skills
teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
plan-review-prompt-refresh-after-plan-edits
Refresh reviewer prompt files from the latest on-disk plan before every adversarial re-review. Prevents Codex/Gemini from critiquing stale plan text after local edits.
tdd-verification-and-adversarial-review
Verify pre-written TDD tests pass, conduct adversarial code review on committed diffs, and route findings to existing issues
multi-role-agent-contract-review-pipeline
Execute a 4-role agent team (Planner/Architect/Reviewer/Integrator) pipeline for self-reviewing knowledge artifacts before delivery
gsd-adversarial-review-pattern
Catch hidden test failures by running adversarial review on sparse-data edge cases before final push
adversarial-code-review-tdd
Systematic adversarial review pattern to identify breaking assumptions in already-passing test suites
adversarial-code-review-for-committed-diffs
Systematic process for reviewing already-committed code changes to catch type inconsistencies, edge cases, and docstring gaps
adversarial-code-review-and-fix
Systematic pattern for catching design flaws in already-passing code through adversarial review, then fixing them with TDD confirmation.
learned-git-worktree-hook-path-and-real-hook-shape-review
Catch hook-installation and governance bugs that only appear in linked git worktrees or against the real generated hook shape, not simplified test fixtures.
ten-agent-pre-plan-review-wave
Launch and verify a 10-agent planning-only wave that moves open GitHub issues into status:plan-review using one isolated worktree per issue, wave-specific continuation cron, and post-run artifact-reconciliation checks.
static-site-build-artifact-plan-review
Plan-review pattern for static-site fixes where the deployed artifact is generated from source files (e.g. sitemap/robots/static assets). Prevents review churn by separating durable regression checks from one-time migration verification and by validating built output, not just source files.
preserved-plan-refile-with-attested-review-wave
Reopen a previously closed GitHub issue with a preserved local plan, rewrite it into a conservative draft, and drive iterative attested adversarial review waves until it is truly approval-ready.