Pace
← All cookbooks Legal cookbook

Legal

NDA triage in minutes. Clause-by-clause playbook checks. Drafting that matches your standard language.

Marquee recipe

NDA triage queue

The legal queue drains five times faster, every standard NDA auto-redlined.

Trigger
Routine, API trigger fired by your email tool's inbound webhook
Skills
triage-nda, review-contract
Features
Routines (API trigger), Gmail/Outlook connector, playbook context, plan mode for the redline

Inbound NDAs hit triage-nda first, which classifies the agreement. Standard ones get an auto-redline against your playbook; non-standard get flagged with the specific clause that needs human review. The legal queue drains 5x faster.

How to set it up

  1. 1
    Install the legal plugin + write your playbook

    The plugin ships with skills; the playbook is your team's standard positions on common clauses (e.g. mutual NDA, IP assignment, liability caps).

    Install in Cowork ↗ claude plugin install legal@pace
  2. 2
    Set up the playbook in a docs folder

    Run setup-engineering-skills once at your repo or workspace root. It scaffolds docs/agents/legal-playbook.md for you. Drop your team's standard positions on common clauses there. The legal skills read from this on every call.

  3. 3
    Create an API-triggered routine

    In Cowork, open Routines → New routine → API trigger. After saving, click Generate token and copy both the URL and the bearer token (shown once).

  4. 4
    Wire your inbox to POST inbound NDAs

    Set up a Gmail/Outlook forwarding rule (or Zapier) that POSTs new emails with subject containing "NDA" to your routine's /fire endpoint, with the email body in the text field of the JSON payload. Paste this as the routine prompt:

    Routine prompt 
    An inbound NDA just arrived. The email body is in the
incoming text field. Run triage-nda to classify
it (mutual / one-way, standard / non-standard, urgency).

If the triage says "standard": run review-contract
with our playbook in the context. Produce a redlined
version as a draft response with explanatory comments.

If "non-standard": post a Slack message in #legal-queue
flagging the specific clause(s) that need a human and
the urgency level. Do NOT auto-redline non-standard
agreements.
  5. 5
    Test with a real (sample) NDA

    Forward a sample NDA to the configured address. Within a couple minutes you'll either see a redlined draft (standard) or a flag in #legal-queue (non-standard). Once you trust the triage classifier, the queue stays drained automatically.

NDA fast-path: redline against your template, in under five minutes

Trigger
Cowork hook, when a counter-party uploads an NDA
Skills
nda-review
Features
Cowork hooks (file upload), Box connector for template lookup, plan mode for review

The hook diffs the inbound NDA against your standard template and produces a redlined version with explanations next to each change. Plan mode parks the redline for your sign-off; one click posts it back to the requester. Frees up the lawyer for the agreements that actually need them.

How to set it up

  1. 1
    Create the Cowork hook

    In Cowork, open Hooks → New hook. Match the trigger described above (file upload, message, schedule).

  2. 2
    Paste this as the routine prompt
    NDA redline prompt 
    When a counter-party uploads an NDA to the legal intake folder, diff it against our standard template. For each meaningful change, annotate next to it: what changed, whether it's acceptable per the playbook, and the suggested counter (if any).

Park the redline in plan mode for the lawyer to sign off. Once approved, post the redlined version back to the requester via email.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.

Quarterly compliance audit prep

Trigger
Routine, schedule, last business day of each quarter
Skills
compliance-question, risk-assessment
Features
Routines (cloud schedule), GitHub + Box connectors, multi-step audit walk

Walks the current state against your compliance framework (SOC 2, GDPR, HIPAA, whichever applies), produces the gap report, and stages evidence requests as Linear tickets routed to the right owners. The first run is the longest; subsequent quarters compare deltas.

How to set it up

  1. 1
    Create the scheduled routine in Cowork

    In Cowork, open Routines → New routine → Schedule. Match the cadence described in the trigger above.

  2. 2
    Paste this as the routine prompt
    Compliance audit prep prompt 
    On the last business day of every quarter, walk the current state of our compliance framework (SOC 2 + GDPR, whichever applies). For each control, check the evidence is current. For gaps, draft an evidence-request Linear ticket routed to the owner who handles that control.

Produce a quarterly gap report: what's in place, what's pending, what's overdue.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.

Vendor security review, alongside the legal review

When a new vendor enters procurement, a routine runs in parallel: legal reviews the MSA against the playbook, while a security skill pulls the vendor's SOC 2 report, parses key controls, flags any gaps against your security policy. Procurement gets one consolidated brief instead of waiting on two separate reviews.

Trigger
Routine, API trigger fired by procurement workflow
Skills
contract-review, risk-assessment
Features
Routines (API trigger), Box connector (for SOC 2 reports + policy docs), parallel skill execution
Vendor security review prompt 
When a new vendor enters procurement, run two reviews in parallel:

1. Legal: contract-review against the MSA playbook (standard terms, liability, data processing).
2. Security: pull the vendor's SOC 2 report from their trust center, parse key controls, compare against our security policy. Flag any gaps.

Roll both into a single procurement brief: legal recommendation, security recommendation, combined go / no-go.