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.

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.

    /legal:contract-review this MSA from $vendor

  • NDA triage

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

    /legal:nda-review their template vs ours

  • Compliance question

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

    /legal:compliance-question can we collect EU user data this way?

  • Risk assessment

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

    /legal:risk-assessment for the new payment processor integration

  • Templated response

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

    /legal:templated-response for this inbound enforcement query

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 /legal:* read precedent docs. Without them, each review is from scratch.

  • Low-stakes NDAs first

    /legal: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 /legal: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 /legal: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 /legal: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