The Markdown file that wiped billions off

The Files in question

**.**

└── **1.0.0**
    ├── **.claude-plugin**
    │   └── plugin.json
    ├── .mcp.json
    ├── **commands**
    │   ├── brief.md
    │   ├── respond.md
    │   ├── review-contract.md
    │   ├── triage-nda.md
    │   └── vendor-check.md
    ├── CONNECTORS.md
    ├── LICENSE
    ├── README.md
    └── **skills**
        ├── **canned-responses**
        │   └── SKILL.md
        ├── **compliance**
        │   └── SKILL.md
        ├── **contract-review**
        │   └── SKILL.md
        ├── **legal-risk-assessment**
        │   └── SKILL.md
        ├── **meeting-briefing**
        │   └── SKILL.md
        └── **nda-triage**
            └── SKILL.md

1. Setup

2. Customisation

Readme.md Besides the installation information, there is important customisation that is possible.

In your project’s .claude/ directory, create a legal.local.md file:

# Legal Playbook Configuration
 
## Contract Review Positions
 
### Limitation of Liability
- Standard position: Mutual cap at 12 months of fees paid/payable
- Acceptable range: 6-24 months of fees
- Escalation trigger: Uncapped liability, consequential damages inclusion
 
### Indemnification
- Standard position: Mutual indemnification for IP infringement and data breach
- Acceptable: Indemnification limited to third-party claims only
- Escalation trigger: Unilateral indemnification obligations, uncapped indemnification
 
### IP Ownership
- Standard position: Each party retains pre-existing IP; customer owns customer data
- Escalation trigger: Broad IP assignment clauses, work-for-hire provisions for pre-existing IP
 
### Data Protection
- Standard position: Require DPA for any personal data processing
- Requirements: Sub-processor notification, data deletion on termination, breach notification within 72 hours
- Escalation trigger: No DPA offered, cross-border transfer without safeguards
 
### Term and Termination
- Standard position: Annual term with 30-day termination for convenience
- Acceptable: Multi-year with termination for convenience after initial term
- Escalation trigger: Auto-renewal without notice period, no termination for convenience
 
### Governing Law
- Preferred: [Your jurisdiction]
- Acceptable: Major commercial jurisdictions (NY, DE, CA, England & Wales)
- Escalation trigger: Non-standard jurisdictions, mandatory arbitration in unfavorable venue
 
## NDA Defaults
- Mutual obligations required
- Term: 2-3 years standard, 5 years for trade secrets
- Standard carveouts: independently developed, publicly available, rightfully received from third party
- Residuals clause: acceptable if narrowly scoped
 
## Response Templates
Configure paths to your template files or define inline templates for common inquiries.

3. Connect your tools

The plugin works best when connected to your existing tools via MCP. Pre-configured servers include Slack, Box, Egnyte, Atlassian, and Microsoft 365. See CONNECTORS.md for the full list of supported categories and options.

Commands

/review-contract — Contract Review Against Playbook

Review a contract against your organization’s negotiation playbook. Flags deviations, generates redlines, and provides business impact analysis.

/review-contract

Accepts: file upload, URL, or pasted contract text. Will ask for context (your side, deadline, focus areas) and review clause-by-clause against your configured playbook.

/triage-nda — NDA Pre-Screening

Rapid triage of incoming NDAs against standard criteria. Categorizes as GREEN (standard approval), YELLOW (counsel review), or RED (significant issues).

/triage-nda

/vendor-check — Vendor Agreement Status

Check the status of existing agreements with a vendor across your connected systems.

/vendor-check [vendor name]

Reports on existing NDAs, MSAs, DPAs, expiration dates, and key terms.

/brief — Legal Team Briefing

Generate contextual briefings for your legal work.

/brief daily          # Morning brief of legal-relevant items
/brief topic [query]  # Research brief on a specific legal question
/brief incident       # Rapid brief on a developing situation

/respond — Generate Templated Response

Generate a response from your configured templates for common inquiry types.

/respond [inquiry-type]

Supported inquiry types include: data subject request, discovery hold, vendor question, NDA request, and custom categories you define.

Skills

Skill	Description
contract-review	Playbook-based contract analysis, deviation classification, redline generation
nda-triage	NDA screening criteria, classification rules, routing recommendations
compliance	Privacy regulations (GDPR, CCPA), DPA review, data subject requests
canned-responses	Template management, response categories, escalation triggers
legal-risk-assessment	Risk severity framework, classification levels, escalation criteria
meeting-briefing	Meeting prep methodology, context gathering, action item tracking

Example Workflows

Contract Review

1. Receive a vendor contract via email
2. Run /review-contract and upload the document
3. Provide context: “We are the customer, need to close by end of quarter, focus on data protection and liability”
4. Receive clause-by-clause analysis with GREEN/YELLOW/RED flags
5. Get specific redline language for YELLOW and RED items
6. Share the analysis with your deal team

NDA Triage

1. Sales team sends an NDA from a new prospect
2. Run /triage-nda and paste or upload the NDA
3. Get instant classification: GREEN (route for signature), YELLOW (specific issues to review), or RED (needs full counsel review)
4. For GREEN NDAs, approve directly; for YELLOW/RED, address flagged issues

Daily Brief

1. Start your morning with /brief daily
2. Get a summary of overnight contract requests, compliance questions, upcoming deadlines, and calendar items needing legal prep
3. Prioritize your day based on urgency and deadlines

Vendor Check

1. Business team asks about a new engagement with an existing vendor
2. Run /vendor-check Acme Corp
3. See existing agreements, expiration dates, and key terms at a glance
4. Know immediately whether you need a new NDA or can proceed under existing terms

MCP Integration

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

The plugin connects to your tools through MCP (Model Context Protocol) servers:

Category	Examples	Purpose
Chat	Slack, Teams	Team requests, notifications, triage
Cloud storage	Box, Egnyte	Playbooks, templates, precedents
Office suite	Microsoft 365	Email, calendar, documents
Project tracker	Atlassian (Jira/Confluence)	Matter tracking, tasks

See CONNECTORS.md for the full list of supported integrations, including CLM, CRM, e-signature, and additional options.

Configure connections in .mcp.json. The plugin gracefully degrades when tools are unavailable — it will note gaps and suggest manual checks.