From ai-brain-starter
Deploys pre-configured legal pack for ai-brain-starter substrate with typed-memory categories for matter management, privilege handling, ABA Model Rule 1.15 retention defaults, and connectors for Clio, NetDocuments, iManage. Use for onboarding law firms or legal teams.
npx claudepluginhub adelaidasofia/ai-brain-starterinit | status | rebuild [--matter <id>]This skill uses the workspace's default tool permissions.
A pre-configured pack that turns the empty substrate into a legal-ready system in one install. The pack ships typed-memory categories that match how a matter actually moves, connectors for the three platforms most firms already pay for, retention defaults that map to the ABA Model Rules, and decision-audit patterns for privilege handling and conflicts checks.
Manages end-to-end external local counsel lifecycle in multi-jurisdiction legal matters: selection, engagement setup, instruction design, performance monitoring, scope enforcement, escalation. Use for LC selection, instructions, check-ins, scope disputes, performance issues.
Configures ai-brain-starter substrate for finance ops with typed-memory categories for deals, counterparties, SOX 404 controls, audit evidence; Workday, NetSuite, SAP connectors; SOX/SEC retention defaults and audit trails. Use for CFO/audit onboarding.
Generates templated responses to legal inquiries like DSARs, subpoenas, NDAs, and litigation holds, with escalation checks for complex cases requiring professional review.
Share bugs, ideas, or general feedback.
A pre-configured pack that turns the empty substrate into a legal-ready system in one install. The pack ships typed-memory categories that match how a matter actually moves, connectors for the three platforms most firms already pay for, retention defaults that map to the ABA Model Rules, and decision-audit patterns for privilege handling and conflicts checks.
A blank install of the substrate forces every legal team to invent the same vocabulary on day one: what is a matter, what is a privileged document, what is a conflicts check, how long do we keep depositions. The vocabulary is not novel. Every firm in North America runs roughly the same primitives, with the same retention obligations, against roughly the same three document management platforms.
This pack ships the primitives so the firm can spend day one on what is actually theirs (their playbooks, their authority chain, their client list) instead of re-deriving the category structure.
Run /vertical-legal init and the pack writes:
| Layer | What ships | Where it lands |
|---|---|---|
| Schema | 8 typed-memory categories with frontmatter contracts | schema/typed-memory-categories.md |
| Connectors | Clio, NetDocuments, iManage specs and OAuth flows | connectors/*.md |
| Retention | Per-category retention rules mapped to ABA Model Rule 1.15 and state variations | retention/defaults.md |
| Decision audit | Privilege-handling guardrails and conflicts-check pattern | decision-audit/*.md |
Nothing is auto-applied to a live install. The pack stages drafts under drafts/ and prints the path; the firm reviews and accepts before merging into the production memory layer.
See schema/typed-memory-categories.md for required and optional frontmatter on each.
connectors/clio.md — Clio API, OAuth2, per-firm key, sync cadence, write-back rulesconnectors/netdocuments.md — NetDocuments REST and ndOffice APIconnectors/imanage.md — iManage Work API and Work Server RESTMapped against ABA Model Rule 1.15 and the most common state-bar variations. See retention/defaults.md for the table. Highlights:
decision-audit/privilege-handling.md — privileged documents cannot leave the matter scope; any agent action that would expose privileged content blocks at write time and surfaces a recoverable error to the operator. Every privilege-related read and write is logged with the matter ID, the requesting role, and the disposition.decision-audit/conflicts-check.md — every new client adds to the conflicts graph; every new matter checks the conflicts graph at intake and blocks if a conflict is detected./vertical-legal init
The init command:
drafts/legal/./vertical-legal status
Reports which categories are live, which connectors have been configured with credentials, and which retention rules have been overridden locally.
Every retention default in retention/defaults.md cites the rule it maps to. Every connector spec cites the official API documentation URL and the auth scheme. Every decision-audit pattern cites the regulatory or ethical rule it enforces. Drafts without provenance are a bug; surface them as gaps in the firm's review pass rather than guessing.