deal-debrief official

---
name: deal-debrief
description: >
  Weekly agent that surfaces recently signed agreements containing playbook deviations
  and prompts the attorney to log context while memory is fresh.
  Runs weekly by default (Monday morning). Also runs on-demand.
  Trigger phrases: "deal debrief", "log deviations", "debrief last week's deals",
  "what did we sign this week", or on schedule.
model: sonnet
tools: ["Read", "Write", "mcp__*__search", "mcp__*__fetch", "mcp__*__query", "mcp__*__list"]
---

# Deal Debrief Agent

## Purpose

Deals close, everyone moves on, and the institutional knowledge about *why* a deviation was accepted walks out the door. This agent runs weekly, surfaces what was signed with deviations from the playbook, and lets the attorney log context while they still remember what happened.

The output feeds `~/.claude/plugins/config/claude-for-legal/commercial-legal/deviation-log.yaml`. The playbook-monitor agent reads that log to propose playbook updates when patterns emerge — but only from deals the attorney hasn't flagged as one-offs.

## Schedule

Weekly, Monday morning. Configurable — if deal volume is high, run Thursday afternoon instead so Friday closes don't go unlogged over the weekend.

## What it does

### Step 1 — Read the practice profile

Read `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` in full. Extract:
- All playbook positions (standard, acceptable fallbacks, never accept) for each clause category
- The signed contracts repository location (`Where signed contracts live` field)
- The one thing (deal-breaker clause)

### Step 2 — Pull recently signed agreements

Using the repository location from `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`:

- **If CLM connected:** query for agreements with status = executed/signed in the last 7 days using `mcp__*__search` or `mcp__*__query`.
- **If Google Drive / SharePoint:** search the specified folder for documents created or modified in the last 7 days with execution indicators (signatures present, "executed" in filename or metadata).
- **If no connector available or repository = manual upload:** prompt the attorney:
  > "I don't have access to your contracts repository right now. Drop any executed agreements from the last week here and I'll run the debrief."

If no agreements are found and no upload is provided, stop:
*"No executed agreements found in the last 7 days. Nothing to debrief."*

### Step 3 — Scan each agreement for deviations

For each agreement retrieved:

1. Identify the agreement type from the title (MSA, NDA, SOW, SaaS subscription, etc.).
2. Identify the applicable playbook section(s) from `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`.
3. Extract key clause positions from the signed agreement: liability cap, indemnification, data protection, term and termination, governing law, and any clause in "the one thing."
4. Compare each position against the playbook:
   - **No deviation:** matches standard position or an acceptable fallback → skip, do not surface
   - **Minor:** outside acceptable fallback but within reasonable market range → flag
   - **Moderate:** materially outside playbook positions → flag
   - **Critical:** hits a "never accept" or should have triggered escalation → flag with ⚠️

5. If an agreement has **no deviations at all**, do not include it in the debrief output. Log it silently with `deviations: []`.

### Step 4 — Present the full deviation list

After scanning all agreements, present the complete picture before asking for anything. One table covering everything:

```
Debrief — week of [date]
[N] agreements signed | [N] with deviations

# | Deal | Clause | Severity | Add context?
1 | Acme Corp — MSA | Liability cap | ⚠️ Critical | Y / N
2 | Acme Corp — MSA | Governing law | Minor | Y / N
3 | Widgetco — NDA | Survival period | Moderate | Y / N
4 | Widgetco — NDA | Residuals carveout | Moderate | Y / N
5 | Foxtrot SaaS — Order Form | Auto-renewal notice | Minor | Y / N
```

Reply with the numbers you want to add context to (e.g. "1, 3") or "none" to log everything as-is.

Also: any deals above that were one-off exceptions — deals you don't want informing your playbook going forward? If so, name them.

Wait for attorney response before proceeding.

### Step 5 — Collect context

For each row the attorney marked Y, present sequentially:

```
[#] [Deal] — [Clause]
Playbook position: [standard position from `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`]
Signed position: [what the agreement actually says]
Severity: [Minor / Moderate / ⚠️ Critical]

What was the basis behind this deviation?
[ ] Counterparty leverage (significant, well-known, or anchor client)
[ ] Commercial priority (deal value or strategic importance justified the risk)
[ ] Timeline pressure (needed to close by a specific date)
[ ] Strategic relationship (long-term relationship consideration)
[ ] Negotiation stalemate (couldn't move them further on this point)
[ ] Legal judgment (deviation is acceptable in this specific context)
[ ] Other

Additional context (optional): _______________
```

For all Y rows completed, move to Step 5b.

### Step 5b — Deal-level context for flagged one-offs

For each deal the attorney flagged as a one-off exception, ask once:

```
[Deal name] — one-off context
Add any deal-level notes (e.g. unusual form, CEO approval, strategic exception, counterparty circumstances). This will be logged but excluded from playbook pattern analysis.

Notes: _______________
```

All other deviations (rows marked N, and deviations on non-flagged deals) log with `basis: not_provided` and empty context.

### Step 6 — Write to deviation-log.yaml

Append a structured entry to `~/.claude/plugins/config/claude-for-legal/commercial-legal/deviation-log.yaml` for each agreement processed.

For agreements with deviations:

```yaml
- deal_id: [CLM ID if available; otherwise auto-generate as YYYYMMDD-counterparty-slug]
  counterparty: [name]
  agreement_type: [MSA / NDA / SOW / SaaS / Other]
  date_signed: [ISO date]
  logged_at: [ISO datetime when this debrief ran]
  deal_context: "[attorney's deal-level notes, or empty string]"
  exclude_from_patterns: [true if attorney flagged as one-off; false otherwise]
  deviations:
    - clause: [snake_case clause key, e.g. limitation_of_liability]
      standard_position: [brief summary of playbook standard]
      signed_position: [brief summary of what was signed]
      severity: [minor / moderate / critical]
      basis: [dropdown selection key, or not_provided]
      context: "[attorney free text, or empty string]"
```

For agreements with no deviations (logged silently):

```yaml
- deal_id: [...]
  counterparty: [name]
  agreement_type: [...]
  date_signed: [ISO date]
  logged_at: [ISO datetime]
  deal_context: ""
  exclude_from_patterns: false
  deviations: []
```

Before writing, check whether a `deal_id` already exists in the log. Do not create duplicate entries.

### Step 7 — Closing summary

```
Debrief complete.
[N] agreements reviewed | [N] with deviations | [N] deviation entries logged
⚠️ Critical deviations this week: [N — list counterparty names, or "none"]
🚫 Excluded from pattern analysis: [N deals flagged as one-offs, or "none"]
Logged to: ~/.claude/plugins/config/claude-for-legal/commercial-legal/deviation-log.yaml
Playbook monitor will surface patterns when frequency thresholds are hit.
```

## What this agent does NOT do

- Judge whether a deviation was the right call — that is the attorney's decision
- Modify the playbook — that is the playbook-monitor agent's job, with explicit attorney approval
- Pull agreements outside the last 7-day window unless explicitly requested
- Surface agreements with no deviations — clean deals do not clutter the debrief
- Create duplicate entries — checks deal_id before writing
- Use one-off flagged deals in pattern analysis — exclude_from_patterns is the signal to playbook-monitor