Pace
All teams / Legal

Legal

Contract review, NDA triage, compliance, risk assessment.

In-house legal teams field high volumes of similar work: NDAs, vendor agreements, employment letters, compliance questions. Pace triages, drafts, and flags risk so you spend less time on routine and more on the actual hard problems. Final calls still stay human; Pace is research + first-pass review, not legal advice.

Install for Legal

The full legal starter set is 2 plugins. Pick the install path that matches you.

Cowork (no terminal)

Click each link below; Cowork opens and asks you to confirm. Restart Cowork after the last one so connectors register.

  1. 1 Install legal
  2. 2 Install operations
After the last install, restart Cowork. The MCP servers (Slack, HubSpot, etc.) only register cleanly on a fresh app start. Quit the app fully, then reopen it.

Terminal (one command)

If you have claude on your PATH already, this installs the whole set in one go.

npx pace-tools install legal operations

pace-tools wraps claude plugin install; runs claude plugin marketplace add GoldenBerry-SO/Pace automatically if you haven't registered the marketplace yet.

Plugins to install

Pick from this set for the role. Primary plugins are essential; companions multiply value.

  • legal primary

    Contract review, NDA triage, compliance Q&A, risk assessment, templated responses.

    claude plugin install legal@pace
  • operations companion

    Vendor management and procurement workflows that legal touches.

    claude plugin install operations@pace

Connectors to set up

Claude prompts to authorize each one the first time a relevant skill fires. You only do this once per project.

  • Slack
  • Box
  • Egnyte
  • Jira
  • Microsoft 365

Workflows

Common ways teams use these plugins day to day. Each one is a starting point; adapt the prompt to your context.

  • Contract review

    Reads a contract (MSA, SOW, service agreement) and flags clauses that diverge from your playbook: liability, indemnification, IP, term, termination.

    Review this MSA from the vendor. Flag anything unusual against our standard terms.

  • NDA triage

    Compares an inbound NDA against your standard template and flags material deviations. Suggests redlines.

    Compare their NDA template to ours. Where are the deltas, which matter.

  • Compliance question

    Researches a question against the relevant framework (GDPR, SOC 2, HIPAA, etc.) and summarizes; not legal advice, research help.

    Compliance question: can we collect EU user data this way? Walk through GDPR.

  • Risk assessment

    Generates a risk register for a new product feature, vendor, or initiative. Categorizes by likelihood and impact.

    Risk-assess the new payment processor integration. What needs vendor diligence, what needs SOC.

  • Templated response

    Drafts a response for a common recurring request (enforcement letter, subpoena acknowledgement, employment verification).

    Draft a response to this inbound enforcement query. Match our standard tone.

Just say it

You don't have to memorize slash commands. After installing, type natural sentences into Claude and the right skill will fire. Each row is a real example.

  • You say

    Triage this NDA from a new vendor

    Claude triggers triage-nda
  • You say

    Review this MSA against our playbook

    Claude triggers review-contract
  • You say

    Check if our terms comply with GDPR

    Claude triggers compliance-check
  • You say

    Brief me on the upcoming board meeting

    Claude triggers meeting-briefing
  • You say

    Assess legal risk for this new partnership

    Claude triggers legal-risk-assessment
  • You say

    Run a vendor check before we sign

    Claude triggers vendor-check

Tips & tricks

Field-tested patterns from teams that have already shipped a quarter or two on these plugins.

  • Connect your document store

    Box or Egnyte connectors let the legal plugin read precedent docs. Without them, each review is from scratch.

  • Low-stakes NDAs first

    `nda-review` on inbound NDAs that match standard patterns is a huge time saver. Reserve human review for bespoke or high-stakes.

  • Compliance question ≠ legal advice

    Treat `compliance-question` output as research. Final call stays with you. The skill is good at surfacing precedent and frameworks, not making the decision.

  • Build templated responses for repeats

    After three similar inbound questions, write a `templated-response`. Saves the fourth, fifth, and sixth.

  • Wrap in /pace router

    For your standard contract review playbook, build a /pace router command that wraps `contract-review` with your specific flags. Reuse beats re-prompting.

  • Document the why

    When Pace flags a clause, document why it matters in your playbook. The next reviewer (human or Pace) benefits.

See also