Playbooks

Curated multi-step legal flows at /admin/legal/playbooks. Each playbook wraps the Custom-workflow runner with pre-baked step prompts.

Shipped playbooks

NDA review checklist

Three-step sweep: (1) extract material terms, (2) audit against a five-point standard (CI definition / term / permitted use / return-destroy / carve-outs), (3) propose 3-5 priority edits with concrete replacement language.

Due-diligence request list

Two-step: (1) identify applicable diligence areas based on deal description, (2) generate per-area request list grouped by area. Covers corporate / commercial / IP / employment / litigation / regulatory / financial-tax / real-estate / data-privacy / ESG.

50-state survey outline

Three-step scaffold: (1) map topic to federal framework + uniform acts + common-law rule, (2) cluster states into 4-6 patterns + flag outliers needing bespoke research, (3) produce markdown scaffold an associate fills in per state.

Negotiation review (with fallback ladder)

Three-step for pre-call prep. (1) Extract material clauses, (2) score each from the user’s posture (aggressive_user / market / aggressive_counterparty), (3) produce a three-rung ladder per clause: ideal language / market fallback / walkaway. Posture-aware — state your posture on the first input line (“buy-side”, “licensee”).

Running

Pick a card → playbook input form opens. Each playbook’s input_prompt tells you what shape of input it expects.

Output renders per-step (markdown for tables, JSON for extracted data). Final output also persists to the same legal_custom_workflow_runs table as custom workflows so Why traces are inspectable.

Adding playbooks

Code-defined in services/legal_playbooks.py. Each playbook is a Playbook dataclass with a tuple of step dicts. Adding one is a one-file change — no migration.

Permissions

Available to roles: partner, attorney, paralegal (via the pollenix.legal role pack).