Grok Bot for Legal Ops (1:1 prep, Slack triage, contract workflows)
法务的会前准备和跟踪表，交给 Bot 维护。 Let a bot keep legal’s prep and trackers current.
SpaceXAI 法务运营 Kelly Noguchi 2026-09-24 官方指南：律师 1:1 前，Bot 翻 Slack、Notion、会议记录和跟踪表起草议程，会后把决定写回对应页面；盯法务相关频道里没人回、口径打架的问题；从 Slack 请求自动维护「待法务审」跟踪表，并补上商机和报价快照；在合同系统里查流程和状态，经明确要求才帮你把已批文件放进流程，写入前先预览确认。原来靠 Cursor 自动化 + Google Apps Script 跑的表，现在全搬进 Grok Bot。可借鉴的规矩：按流程拆 Bot、对外消息一律先草稿再人发、读和写系统分开。 Official guide by SpaceXAI Legal Ops’ Kelly Noguchi, Sep 24, 2026. Before attorney 1:1s the bot drafts an agenda from Slack, Notion, notes, and trackers, then writes decisions back afterward; it watches legal channels for unanswered or conflicting guidance; it maintains a Legal Review tracker from Slack intakes enriched with deal and quote snapshots; in the contract system it looks up workflows and, only on explicit request, moves approved documents with a preview before any write. A tracker that used to run on Cursor automation plus Google Apps Script now runs fully in Grok Bot. Portable rules: one bot per workflow, draft-then-human-send for outbound messages, separate read and write paths.
为什么推荐Why we recommend it 官方 Guides（2026-09-24）。收录理由：少见的法务岗位实例，而且写清了「哪些只读、哪些写之前要预览」。边界：依赖 Ironclad、Salesforce 等企业系统；法律判断仍由律师做。本库未实测。 Official Guides (Sep 24, 2026). Why listed: a rare legal-team example that spells out what stays read-only and what needs a preview before writing. Boundary: relies on enterprise systems like Ironclad and Salesforce; legal judgment stays with attorneys. Not tested here.
整理、查资料、起草可以自动；对外消息、写入合同系统和 CRM 前都要人确认。 Organizing, research, and drafting can run on their own; outbound messages and writes to the contract system or CRM need a person first.
先在可撤回、不外发的范围内试跑。本条未批准前：整理、查资料、起草可以自动；对外消息、写入合同系统和 CRM 前都要人确认。。 Try it first in a reversible, non-outbound scope. Until approved: Organizing, research, and drafting can run on their own; outbound messages and writes to the contract system or CRM need a person first..
把跑通的步骤存成 Skill，下次同类任务直接复用，而不是重新口述。 Save the working steps as a Skill so the next similar job reuses them instead of being re-explained.
输出稳定后再打开例行 / 定时。本条已有例行形态，不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.
