$ loading_
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legal_hold fields in _log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "legal-hold" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/legal-hold/SKILL.md 2. Save it as ~/.claude/skills/legal-hold/SKILL.md 3. Reload skills and tell me it's ready
--status (no slug): read _log.yaml, produce portfolio-wide hold report.~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md + log row.~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → privilege markings, hold template pointer, escalation norms.--issue: capture scope, custodians, date range, systems. Draft legal-hold-v1.docx. Update legal_hold fields. Append history entry. Set next_refresh (default +6mo).--refresh: capture scope/custodian changes. Draft next version. Update last_refresh + next_refresh. Flag departed custodians.--release: capture release date, retention instruction. Draft release notice. Set released: field.A legal hold is the most mechanical high-stakes document in-house counsel writes. The notice itself is templated. The failure modes are operational: issued too late, scoped too narrowly, never refreshed, never released. This skill owns all four phases: issue → refresh → (release) → track.
The portfolio already flags missing holds; this skill writes them.
Preservation duties vary materially by forum. Federal common law (via Zubulake / Residential Funding / Rule 37(e)) differs from state practice; states differ from each other on trigger timing, scope, sanctions, and spoliation remedies; regulatory preservation obligations overlay civil rules in some matters (SEC Rule 17a-4, HIPAA, etc.). The trigger, scope, and sanctions exposure cited in the draft are a starting-point read for the forum named in the matter — confirm with counsel before issuing, refreshing, or releasing.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — log row (legal_hold fields + status)~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md — matter context (counterparty, facts, key custodians from internal_owners)~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md — house style for litigation hold template pointer, privilege marking, escalation normsConflicts gate — unbypassable. Before issuing, refreshing, or releasing a hold, check _log.yaml for the matter slug. If the matter is not in _log.yaml, refuse and route:
"I don't see [matter slug] in the matter log. Run
/litigation-legal:matter-intakefirst so the conflicts check runs and the matter workspace is set up. I won't issue, refresh, or release a legal hold on a matter that hasn't been intaken — the conflicts check is the gate, and a hold issued against an unmanaged matter has no_log.yamlrow to tracklast_refresh/next_refresh/releasedagainst."
Do not proceed on an unintaken matter. Intake is what runs conflicts and writes the _log.yaml row the --refresh / --release / --status flags operate against.
The command takes a flag: --issue | --refresh | --release | --status. Default (no flag) → prompt.
--issue — first issuanceRequired when legal_hold.issued == false and the matter is active or reasonably anticipated.
Before issuing the hold to custodians (the consequential act): Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md. If the Role is Non-lawyer:
Issuing a legal hold has legal consequences — the scope, custodian list, and timing create the preservation record the company will be judged on if spoliation is argued later. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
…
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.
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
Drafts board or committee meeting minutes in your house format. 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. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
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.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
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.