uk-legal-plugins

Trace the current state of a UK Act including in-force amendments AND any pending bills that would amend it. Use whenever the user asks "is <Act> current", "what's the latest version of <Act>", "have any bills amended this", "what's pending for <Act>", or "what changes are proposed to <Act>". Statutes are living documents — a citation without amendment-status risks citing repealed or superseded text.

Trace the parliamentary journey of a UK bill — debates, key contributions, and divisions. Use whenever the user asks "how did the <bill> progress", "who spoke against the <bill>", "what was the vote on <bill>", "show me the Lords debates on <bill>", or "trace the <bill> through Parliament". The skill assembles a chronological view from Bills API + Hansard + Votes data.

Find a UK court judgment by party names and verify its neutral citation before citing it to the user. Use whenever the user asks "find <X v Y>", "get me the citation for <case>", "what's the neutral citation for the <case name>", "is there a case called <name>", or pastes a partial case reference. This skill verifies the case exists in TNA Find Case Law BEFORE reporting the citation — prevents the "plausible-looking but wrong" citation failure that happens when an agent formats from training data.

Construct an OSCOLA citation for a UK case, statute, or Hansard reference AFTER verifying the source exists via uk-legal MCP. Use whenever the user asks to "cite <source> in OSCOLA", "give me the OSCOLA citation for", "format this as OSCOLA", or pastes a partial citation. This skill verifies first and formats second — preventing the most common citation fabrication route where an agent formats plausible-looking fields without confirming the source actually exists.

Retrieve what a named member of either House said in a specific Hansard debate. Use this skill whenever the user asks "what did <peer/MP> say about <topic>", "find <member>'s contribution to the <bill> debate", "did <name> speak on <date>", or "quote <name>'s speech on <subject>". This skill must be used for any peer-or-MP-specific Hansard query — text-searching Hansard by member name returns unrelated debates and is the most common failure mode.

Build or review an element chart — a patent claim chart (infringement, invalidity, or review) or a civil element chart for any cause of action or defence — with every cell pin-cited and gap detection as the priority output. Use when the user asks for a claim chart, element chart, proof chart, infringement or invalidity contention, element-by-element mapping, or asks "what are we missing to prove [claim]".

House cold-start for the UK litigation plugin — branches by role (in-house, firm solicitor, barrister, solo) and side (claimant, defendant, both), captures risk calibration, landscape, and house style, and writes the practice profile CLAUDE.md. Use on a fresh install, when the user wants to set up or redo the practice profile, or to re-check available integrations.

Prepare for a witness examination — build a cross-examination outline or witness statement preparation questions, pull relevant documents, organise topics around the case theory, and surface impeachment or credibility material. Use when the user says "prep for [witness]'s cross-examination", "build a cross-examination outline", "prepare witness statement questions for [name]", or needs to prepare for oral evidence.

Triage a witness summons or third-party disclosure order served on the company — classify it, analyse scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar. Use when the user says "we got a witness summons", "third-party disclosure order", "served with a court order for documents", or shares a witness summons, third-party disclosure order, or regulatory notice to evaluate.

Per-system AI inventory — track each AI system's EU AI Act role and risk tier (where EU nexus exists), UK regulatory flags (ICO DPIA trigger, CMA, FCA model risk, MHRA, Ofcom), and UK GDPR Art. 22 automated decision-making status. Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", "ai system registry", or "uk gdpr automated decisions register".

Run an AI impact assessment — structured intake, risk analysis, UK regulatory classification (UK GDPR / DPA 2018, ICO AI guidance, sector-specific UK regulation), EU AI Act analysis where EU nexus exists, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.

Run the cold-start interview — learns your UK AI governance practice and writes `~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains `[PLACEHOLDER]` markers, or when user says "set up ai governance plugin", "onboard me", "configure ai governance".

Guided customisation of your UK AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customise".

Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when any substantive skill needs to know which matter it's working in.

Keep the AI policy current with practice — weekly sweep of saved AIAs, triage results, and vendor reviews to find policy drift, or direct query for a proposed new AI practice. Checks against UK regulatory commitments and ICO guidance position. Use when user says "policy sweep", "does our AI policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", or on a recurring schedule.

Draft a UK AI usage policy from published UK model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for solicitor review and adoption, not a finished policy. Sources from Law Society AI guidance, ICO AI guidance, SRA risk outlook, sector regulator guidance, and peer policies. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.

Diff a new UK AI regulation, ICO guidance, CMA report, FCA publication, or EU AI Act implementing act against your current governance posture — surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when a UK AI regulation or guidance moves (or you learn about one you missed), or when user says "new guidance just dropped", "does [regulation] affect us", "gap analysis for ICO AI guidance", "compliance check against [UK AI law or guidance]", "EU AI Act gap analysis", or pastes regulatory text.

Classify a proposed AI use case against your registry — approved, conditional, or not approved — and produce required conditions and next steps. Applies UK GDPR Article 22 automated decision-making analysis, ICO AI guidance, and sector-specific UK regulatory flags. Flags cross-plugin handoffs to privacy or product counsel. Use when user says "triage this use case", "can we use AI for X", "is this approved", "what do we need to do to use AI for X".

Review vendor AI terms — agreement, addendum, or ToS AI provisions — against your UK governance positions; flag training-on-data, liability, model changes, and AI policy consistency. Use when user says "review this AI agreement", "check vendor terms", "what did we agree to with [vendor]", "vendor sent an AI addendum", "is this AI contract okay", or attaches vendor AI terms.

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.

Run the cold-start interview to learn your UK commercial contracts practice and write your team practice profile. Use on first use of the plugin, when `~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/CLAUDE.md` is missing or still contains template placeholders, or when the user says "set up the plugin", "configure commercial contracts", "onboard me", or "let's get started". This is the only skill that should run on a fresh install.

Guided customisation of your UK commercial contracts practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, playbook positions, NDA triage preferences, house style, review preferences, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my playbook", "tune my config", or "customise".

Route a contract issue to the right approver per the escalation matrix in `~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/CLAUDE.md`, and draft the ask. Includes UK regulatory referral triggers (CMA, FCA, ICO, Companies House). Use when the user says "who needs to approve this", "escalate this", "does this need Head of Legal sign-off", "route this for approval", or when another skill finds an issue that exceeds the reviewer's authority.

Manage matter workspaces — new, list, switch, close, or detach (practice-level). Use when a multi-client practitioner needs to create a matter, switch the active matter, list matters, archive a matter, or detach to practice-level context, or when another skill needs to know which matter it's working in.

Reference: fast triage of inbound NDAs into GREEN / YELLOW / RED under English law of confidence and common law principles. Built for sales and BD to self-serve before pinging legal. Loaded by /commercial-legal-uk:review when an NDA is detected.

Show contracts with cancel-by deadlines coming up and warn before notice windows close, working from a maintained renewal register. Use when the user asks "what's renewing soon", "what renewals are due", "did we miss a cancellation window", "add this to the renewal tracker", or on a scheduled basis. Receives handoffs from saas-msa-review. Business-day roll-back uses UK bank holidays (E&W by default; Scots bank holidays where governing law is Scots law).

Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.

Review a vendor agreement, NDA, or SaaS subscription against your UK playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.

Reference: review of SaaS subscription agreements under English contract law with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, UK GDPR sub-processor rights, and UCTA 1977 reasonableness. Loaded by /commercial-legal-uk:review when a SaaS or subscription agreement is detected.

Translates a contract review into a summary the business stakeholder will actually read. Not a legal memo — a two-minute answer to "can I sign this and what do I need to know." Use when user says "summarize for the business", "write this up for [stakeholder]", "explain this to procurement", "non-legal summary", or when a review is done and needs to go to someone outside legal.

Reference: review of an inbound vendor agreement against the team playbook in `~/.claude/plugins/config/uk-legal-plugins/commercial-legal-uk/CLAUDE.md` under English contract law (with notes for Scots law / NI where the governing law requires). Flags deviations, assesses risk, generates specific redline language, and routes to the right approver. Loaded by /commercial-legal-uk:review when a vendor MSA, services agreement, or similar is detected.

Detects when Luminance, Kira, or a similar bulk-review tool is in use, hands off the high-volume clause extraction to it, and QAs its output per the trust level in `~/.claude/plugins/config/uk-legal-plugins/corporate-legal-uk/CLAUDE.md`. Use when user says "send to Luminance", "bulk review", "AI extraction", or when diligence-issue-extraction hits a high-volume category.

Drafts board or committee meeting minutes in your house format under the Companies Act 2006. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Handles quorum confirmation, conflict of interest disclosures (CA2006 s.177), and the distinction between decisions that can be made at a meeting versus by written resolution. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", or calendar detection of an upcoming board or committee event.

What's blocking completion — maintain the closing checklist with status, critical path, and days to completion. Self-updating: ingests new items from diligence findings and schedule builds, tracks status, surfaces what's blocking. UK-specific: covers CMA merger control, FCA Part XII change of control, Panel conditions, and CA2006 corporate approvals. Use when user says "closing checklist", "what's left to close", "checklist status", "add to the checklist", or on a scheduled status pull.

House cold-start interview (request list + prior memo), or --new-deal for deal-specific context. Modular: identifies which practice areas apply (M&A, Board & Secretary, Public Company, Entity Management), then asks targeted questions for each active module and writes only the relevant sections to the plugin config under UK law (Companies Act 2006, English M&A practice, FCA/AIM, Companies House). Use on fresh install, when CLAUDE.md still has [PLACEHOLDER] markers, when starting a new deal, or to re-check integrations or refresh a module.

Guided customisation of your corporate practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, active modules (M&A / Board & Secretary / Public Company / Entity Management), materiality thresholds, disclosure schedule format, written resolution precedents, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", or "customise".

Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.

Read VDR documents and extract issues per house categories and materiality thresholds, producing findings in house memo format under English / UK law. Use when user says "review the data room", "extract issues from [folder]", "diligence review", "what's in the VDR", or points at VDR documents.

Entity compliance tracker — initialise, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates Companies House filing deadlines by entity and nation (England & Wales / Scotland / Northern Ireland), and surfaces what's due in the next 30/60/90 days. Covers Confirmation Statements (CS01), annual accounts, PSC register updates, and charge registration (21-day window). Use when user says "entity compliance", "Companies House deadlines", "Confirmation Statement due", "accounts filing", "entity tracker", "what filings are due", "entity health", or "good standing".

Post-completion M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initialises from whatever deal artefacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start. Use when user says "integration", "post-completion", "post-closing", "consents outstanding", "contract assignment", "integration status", or "what's left on the deal".