Legal & Compliance Vault

Plan a legal document and compliance register with owners, deadlines and evidence links. The skill starts by reviewing overdue obligations. It builds empty document records on request.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for a legal document vault, compliance document register, licence register or statutory records. Identify applicable obligations, supporting evidence, sign-off, counsel involvement and review cadence.

It does not provide legal advice or file anything with an authority. A register supports responsibility and review without determining which laws apply to a business. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

The workflow lists obligations, assigns owners, links evidence, tracks due dates and records review or filing. Inputs establish document storage, deadlines, current overdue items and whether an obligation register, document list or both are needed. Its 12 fields are Document Title, Document Type, Compliance Framework, Owner, Department, Effective Date, Expiry Date, Renewal Required, Storage Link, Confidentiality, Status and Legal ID. Document types include Contract, Policy, Invoice, Certificate, Report, ID Proof and Other. Confidentiality options are Internal, Public, Confidential and Restricted; statuses are Draft, In Review, Approved, Active, Expired and Superseded. No relation fields are specified.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_legal_compliance_vault_status ON legal_compliance_vault (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.