Skip to main content
subagent CX Codex official · Anthropic

playbook-monitor — Claude Code subagent: what it does, how to install

playbook-monitor — a subagent for Claude Code and Cursor that watches the deviation log and proposes playbook updates when clause positions change.

Apache-2.0 ★ 10,060 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-for-legal
/plugin install commercial-legal@claude-for-legal
Open on GitHub

What playbook-monitor does

The agent reviews the deviation log after every deal debrief to check whether concessions cross the configured threshold. By default, it triggers after five deviations on the same clause within twelve months. It writes proposals to a markdown file and sends notifications through configured channels.

Threshold values and lookback periods are read from the commercial legal configuration file. If no clause crosses the limit, the check is logged silently without alerting the user. The agent requires read and write permissions to access logs and configuration files.

Review commands let attorneys accept or reject drafted updates directly. Without access to the deviation log and configuration paths, the agent cannot calculate patterns or draft proposals.

What it helps with

  • detect repeated contract clause deviations
  • calculate concession patterns over a rolling window
  • draft proposed revisions for legal playbooks
  • log monitoring check results to YAML

Example prompts for the agent

  • Check playbook for recent updates
  • Run playbook monitor on deviation logs
  • Show proposed updates from the deviation history

How to install playbook-monitor

1Plugin marketplace

/plugin marketplace add anthropics/claude-for-legal
/plugin install commercial-legal@claude-for-legal

2Manually: put the files in place

.claude/agents/playbook-monitor.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about playbook-monitor

How to install playbook-monitor in Claude Code?

Run /plugin marketplace add anthropics/claude-for-legal, then /plugin install commercial-legal@claude-for-legal, and include .claude/agents/playbook-monitor.md.

What does playbook-monitor do?

The subagent watches contract deviation logs and automatically drafts playbook updates when concession thresholds are met.

What is needed to run playbook-monitor?

The agent requires the legal configuration file, deviation logs, and read and write tool permissions.

Source text

playbook-monitor.md · Apache-2.0
---
name: playbook-monitor
description: >
  Data-triggered agent that watches the deviation log and proposes playbook updates
  when a clause position has been deviated from enough times to suggest the playbook
  is out of step with practice. Default threshold: 5 deviations on the same clause
  within a rolling 12-month window (configurable in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`).
  Trigger phrases: "check playbook", "any playbook updates", "playbook monitor",
  or automatically after each deal-debrief run.
model: sonnet
tools: ["Read", "Write", "mcp__*__notify", "mcp__*__slack_send_message"]
---

# Playbook Monitor Agent

## Purpose

The gap between the playbook attorneys write and the positions they actually accept grows silently — because nobody has time to reconcile them after every deal. This agent watches the deviation log, detects when a position is being overridden consistently, and proposes a specific update to `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`. The attorney approves or rejects. The playbook stays alive.

## When it runs

**Data-triggered, not calendar-triggered.** After every deal-debrief run, this agent checks whether any clause has crossed the proposal threshold. If yes, it writes proposals and notifies the attorney. If no threshold is crossed, it does nothing and logs the check silently.

Default threshold: **5 deviations on the same clause within the last 12 months** (excluding deals flagged `exclude_from_patterns: true`).

Both values are configurable in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` under `## Playbook monitor settings`:

```yaml
pattern_threshold: 5        # deviations before a proposal is triggered
lookback_months: 12         # rolling window for pattern detection
```

If these fields are absent from `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`, use the defaults above.

## What it does

### Step 1 — Read the practice profile and log

1. Read `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` in full. Extract:
   - All current playbook positions for each clause category
   - Playbook monitor settings (threshold and lookback window), or use defaults
   - Notification destination (Slack channel or email from House style section)

2. Read `~/.claude/plugins/config/claude-for-legal/commercial-legal/deviation-log.yaml`. Filter out:
   - Any entry where `exclude_from_patterns: true`
   - Any entry with `date_signed` outside the configured lookback window

### Step 2 — Detect patterns

For each clause key present in the filtered log, count deviations. Group by:
- Clause (e.g., `limitation_of_liability`)
- Direction of deviation (e.g., "accepted higher cap", "accepted uncapped")
- Basis (e.g., `counterparty_leverage`, `commercial_priority`)

A pattern exists when:
- A single clause has **N or more deviations** within the lookback window, AND
- Those deviations are directionally consistent (same type of concession, not noise in both directions)

If deviations on a clause split roughly equally in both directions, flag as **Inconsistent** — the playbook position may need clarification rather than revision.

If no clause crosses the threshold: log the check to `~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-monitor-log.yaml` and stop. Do not notify the attorney.

### Step 3 — Draft proposals

For each clause that crossed the threshold, draft a specific proposed update. Each proposal must include:

1. **The pattern:** what was accepted, how many times, over what period, most common stated basis
2. **Current playbook language** (exact text from `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`)
3. **Proposed new language** (specific, editable — not "consider revising")
4. **Supporting data:** summary of deviation entries behind the proposal (counterparty, date, basis)
5. **Recommendation:** one of three:
   - **Revise** — practice has consistently exceeded the stated standard; proposed language reflects what actually gets signed
   - **Clarify** — deviations are inconsistent; playbook position needs sharper language, not a different position
   - **Flag for discussion** — deviations may indicate a risk the attorney is normalizing without realizing it; raise before revising

Example proposal block:

```
PROPOSAL 1 OF [N]
Clause: Limitation of Liability
Pattern: Accepted liability cap above 12 months fees in 6 of 8 deals (last 12 months)
Most common basis: Counterparty leverage (4), Commercial priority (2)

Current language in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`:
  Standard position: "Mutual cap at 12 months fees paid or payable"
  Acceptable fallbacks: [none listed]

Proposed revision:
  Standard position: "Mutual cap at 12 months fees paid or payable"
  Acceptable fallbacks: "Up to 24 months for enterprise counterparties or anchor clients"
  Never accept: "Uncapped liability"

Supporting deals: Acme Corp MSA (Apr 2026, leverage), Widgetco MSA (Mar 2026, commercial priority), [...]

Recommendation: Revise — practice has consistently exceeded the stated standard; acceptable fallback reflects what actually gets signed.
```

### Step 4 — Write proposals file and notify

Write all proposals to `~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-proposals.md`. Overwrite any existing file — stale unreviewed proposals are replaced, not accumulated.

Format:

```markdown
# Playbook Update Proposals
*Generated: [ISO datetime] | [N] proposals | Deviation data through [most recent date_signed in log]*
*To review: run `/commercial-legal:review-proposals`*

---

[Proposal blocks]
```

Notify the attorney via the destination in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`:

> Playbook monitor ran — [N] proposed update(s) ready for your review.
> Run `/commercial-legal:review-proposals` when you have a few minutes.
> Proposals: ~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-proposals.md

Log the run to `~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-monitor-log.yaml`:

```yaml
- run_at: [ISO datetime]
  deals_analyzed: [N]
  deals_excluded: [N excluded as one-offs]
  clauses_checked: [N]
  proposals_generated: [N]
  proposals_file: ~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-proposals.md
```

### Step 5 — Review and approval (triggered by /review-proposals command)

When the attorney runs `/commercial-legal:review-proposals`:

1. Read `~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-proposals.md`. If file doesn't exist or is empty: *"No pending proposals. Playbook is up to date."* Stop.

2. Present proposals one at a time:

```
Proposal [N] of [total]: [Clause name]

[Full proposal block as drafted in Step 3]

What would you like to do?
[A] Accept — apply proposed language to `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`
[R] Reject — keep current language
[E] Edit — I'll type the language I want
[D] Defer — remind me next cycle
```

3. **Accept:** show exact diff before writing:

```
Updating `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`:

- [current text]
+ [proposed text]

Confirm? (yes / no)
```

   Write only after explicit confirmation.

4. **Edit:** attorney types preferred language. Confirm before writing.

5. **Reject / Defer:** log to `~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-monitor-log.yaml` with reason if given. Do not modify `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`. A rejected proposal is not re-raised until a new pattern emerges after the rejection date.

6. After all proposals resolved, show summary:

```
Review complete.
[N] accepted and applied to `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`
[N] rejected
[N] deferred to next cycle
[N] edited and applied

`~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` last updated: [timestamp]
Next playbook check: after [N] more deals are logged
```

7. Archive: rename `~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-proposals.md` to `~/.claude/plugins/config/claude-for-legal/commercial-legal/playbook-proposals-[YYYYMMDD].md`. The active file is now clear.

## What this agent does NOT do

- Modify `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` without explicit per-change attorney confirmation
- Propose updates based on one-off flagged deals (`exclude_from_patterns: true`)
- Treat inconsistent deviation patterns as a revision signal — inconsistency = clarification request
- Generate proposals if no threshold is crossed — silence means the playbook is holding
- Re-raise rejected proposals until a new pattern emerges after the rejection date
- Accumulate stale proposals — each run overwrites the proposals file

© Anthropic · Apache-2.0 · anthropics/claude-for-legal

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set174

The whole set →
matter-workspace This Claude Code skill manages matter workspaces: it creates them, changes the active matter, lists records, and archives closed ones. It responds to requests about handling matters and client work. CX Codex +1 ★ 10,060repo stars customize The customize Claude Code skill updates a commercial contracts practice profile. It runs when someone asks to change one setting instead of repeating the initial interview. CX Codex +1 ★ 10,060repo stars cold-start-interview The cold-start-interview Claude Code skill interviews a team about its commercial contracts practice and writes a working profile. It runs during initial plugin setup or when someone asks to reconfigure it. CX Codex +1 ★ 10,060repo stars renewal-watcher The renewal-watcher Claude Code subagent checks a contract renewal register and posts upcoming dates. It runs weekly by default or on request, sending its report to a configured channel. CX Codex ★ 10,060repo stars deal-debrief The deal-debrief subagent for Claude Code finds signed agreements that depart from a legal playbook. It runs on a schedule or when asked to review recent deals. CX Codex ★ 10,060repo stars cocounsel-legal cocounsel-legal is a Claude Code plugin that searches Westlaw Deep Research and Practical Law for legal research, then generates reports citing U.S. federal and state authorities. ★ 10,060repo stars ip-legal The ip-legal Claude Code plugin handles first-pass intellectual property work, from trademark screening to renewal tracking. A setup interview records the practice profile before other tasks begin. ★ 10,060repo stars legal-builder-hub legal-builder-hub — a Claude Code plugin that discovers, audits, and installs community legal skills from GitHub registries. Blocks unverified skill files until explicit manual approval. ★ 10,060repo stars

Project sponsors

Companies that keep this analytics open