# Contract Playbook Review

Methodology for clause-by-clause review of a contract against a structured deviation...

- Repository: https://github.com/benchflow-ai/skillsbench (1888 stars)
- Category: Business
- License: Apache-2.0
- Last updated: 2026-10-24
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add benchflow-ai/skillsbench --skill contract-playbook-review -g -a claude-code -y`
Codex: `npx skills add benchflow-ai/skillsbench --skill contract-playbook-review -g -a codex -y`
Cursor: `npx skills add benchflow-ai/skillsbench --skill contract-playbook-review -g -a cursor -y`
Gemini CLI: `npx skills add benchflow-ai/skillsbench --skill contract-playbook-review -g -a gemini-cli -y`

## Description

Methodology for clause-by-clause review of a contract against a structured deviation policy ("playbook"). Covers how to walk a playbook, locate the matching provision in the contract, apply rule types (max-value, must-be-present, must-be-absent, acceptable-set, must-have-feature), classify the result (ok / risk / reject), choose the prescribed action, and ground each finding in a verbatim excerpt. Use whenever reviewing any contract, NDA, MSA, vendor DD questionnaire, lease, DPA, against a structured rules-based playbook.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Contract playbook review

How a contract reviewer applies a structured deviation policy to a contract, clause by clause, and emits a structured review.

## The general workflow

A playbook is a list of clause rules. Each rule names a clause, describes the policy in prose, and encodes the policy as machine-checkable fields (e.g. `max_years`, `acceptable_jurisdictions`, `must_be_present`). Review is a four-step loop, repeated once per clause:

1. **Locate** the corresponding provision in the contract (it may not be present at all).
2. **Apply** the rule, check the contract's position against the policy fields.
3. **Classify** the outcome as `ok`, `risk`, or `reject`.
4. **Record** the finding: a verbatim excerpt that grounds it, a rationale, and the playbook's prescribed action.

Walk the playbook in order. Don't skip clauses just because the contract is silent on them, silence is itself a finding (`found = false`) and may trigger an action (e.g. "request_addition").

## Rule types you will see

A handful of rule shapes cover almost every playbook entry. Recognise them and you can apply them mechanically:

| Rule shape | Field example | "ok" means |
|---|---|---|
| Numeric ceiling | `max_years: 3`, `max_months: 24` | Contract value ≤ ceiling |
| Numeric floor | `min_years: 1` | Contract value ≥ floor |
| Must be present | `must_be_present: true` | Provision exists |
| Must be absent | `must_be_absent: true` | Provision (or specific phrasing) does NOT exist |
| Acceptable set | `acceptable_jurisdictions: [...]` | Contract value ∈ set |
| Required feature | `must_allow_destruction: true` | Provision contains the feature |
| Conjunction of features | `must_require_notice && must_require_cooperation` | All features present |
| Conditional structural | `must_be_bilateral_if_present` | Provision absent OR present-and-symmetric |

The rest: https://github.com/benchflow-ai/skillsbench/blob/HEAD/tasks-extra/nda-playbook-review/environment/skills/contract-playbook-review/SKILL.md