LegalQuants Transactional

closing-bible

Audit a transaction closing folder after signing against the agreed closing checklist or the sigpack ledger, and account for the whole set — which version of each document is final, what appears executed and dated, what is missing, duplicated or in version conflict, and a receipt that balances. Use when a lawyer asks to compile, assemble, audit, update or index a closing set or completion bible. Not for preparing or inserting signature pages.

closing-checklist

Draft an editable Word transaction closing checklist from an SPA or other anchor agreement, or propose and apply substantive changes to an existing checklist after revised agreements, additional documents or lawyer instructions. Use for signing/completion deliverables, conditions, approvals and post-closing actions; preserve house formatting, source references and timing. Not routine status chasing, signature-pack assembly or a closing bible.

conform

Adapt a selected clause from a source or precedent document into a core document's own vocabulary, or check a core document for leftover source-document vocabulary, using current /definition-check ledgers for both documents. Use when a lawyer wants to reuse precedent language across documents with different defined-term vocabularies, or wants to check whether precedent language leaked into a core document unchanged.

definition-check

Review a lawyer-provided contract and produce a visual report that annotates defined terms and drafting issues, plus a machine-readable term index that agents can reference during drafting. Use when a lawyer wants to find terms that are used but not defined, used before they are defined, defined but never used, duplicated, inconsistent, or otherwise problematic.

diligence

Use when a data room, deal folder, or contract portfolio needs review against an issue checklist and the lawyer needs factual results they can inspect: every match pin-cited, every agreement accounted for, scoped negatives shown, and everything the run could not resolve kept visible. Builds a file and contract-family manifest, compiles the lawyer's checklist into fixed review schemas, gates twice before the long run, and delivers a coverage-receipted issue/agreement HTML crosswalk plus a further-enquiries register. Trigger on "review this data room", "run diligence", "check these contracts against our list", or a folder of agreements plus any checklist, even without the word diligence.

legaldesign

Create one polished, editable, evidence-grounded HTML explanation of supplied or completed legal work. Use for a self-contained one-pager, a slide brief with a clickable overview, visual companions to advice or findings, reusable templates, and firm color setup. Resolve missing intake before designing; preserve the fixed house components, editor, popups, and client/template exports.

lq-start

Ask which CODEX for Legal skill fits the work in front of you. A map of the installed skills by situation, with one pick and the prompt to type, and a line on what the other LegalQuants plugins add. The same door ships in every LegalQuants plugin. Type it when you do not know what to type. Not for doing legal work, and not a coach.

playbook-builder

Build or update an approved contract playbook from one to five lawyer-selected templates, precedents, negotiated agreements, or KM notes. Use when a lawyer wants to turn source documents into source-linked preferred positions, fallbacks, red lines, approved wording, and optional Matter Lenses. Keep every inferred position as a candidate until the lawyer confirms it. Do not use to review counterparty paper against an existing playbook; use playbook-review.

playbook-review

Review counterparty contracts, outbound drafts, or revised contract packages against an approved Playbook Engine contract playbook. Start from Standard Baseline, suggest but never auto-activate Matter Lenses, prove document and rule coverage, and deliver a clause-anchored issues list showing exact source text, visible suggested inline markup, clean proposed text, and drafting provenance. Do not create or apply a Word redline.

read-redline

Use when a counterparty sends a redline, blackline, or compare PDF, or a Word file with tracked changes, and you need every change, what matters, and a marked-up copy to hand back. Extract PDF changes with the bundled calibrated parser (`pdfplumber`) or Word changes from their tracked-change tags (standard library), render PDF pages with Poppler and look to confirm nothing was missed, rate each change with the significance rubric, and create a separately named annotated copy (`pypdf`) with tier-coloured highlights and plain-English comments without modifying the source. Trigger on "what changed in the new version" or "mark up this compare" even without the word redline.

regulatory

Regulatory research, refreshing earlier research, jurisdiction comparison and legality checks built on primary sources — retrieves the instrument from its official publisher, proves which version it is, and quotes only from the bytes it fetched. Use when the user has a regulation problem: understanding what a law requires, checking whether text they hold is current, re-running earlier research against the instrument as it stands today, or comparing how a rule differs across markets. Domain- and sector-agnostic: any instrument, country or area of law. Trigger even without the word "regulatory" — e.g. "what does the AI Act require," "is this still in force," "has this changed since we advised," "how does this differ in the UK," "we're planning to launch X, where does that land," "find me the actual text of," "is our compliance memo out of date." Answers questions about legal requirements with cited support; identifies unresolved facts and judgments without deciding disputed application questions.

sigpack

Use for wet-ink and mixed closings on a folder of execution PDFs: find every signature page, read who signs (party, signatory, capacity), open the matter ledger, build the signature packs by agreement, counterparty or signatory with the instructions table and cover note; then, as signed pages come back over days as scans, native PDFs or e-signature envelopes, look at each one, place only the signed ones back where their unsigned page was, and keep the receipt that says what is signed, blank, missing or unmatched until the closing is complete. Trigger on "signature packs", "sig pages", "signing bundle", "compile the executed versions", "insert the signed pages back", "what's still outstanding".