$ loading_
Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "matter-update" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/matter-update/SKILL.md 2. 保存为 ~/.claude/skills/matter-update/SKILL.md 3. 装好后重载技能，告诉我可以用了
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/ and _log.yaml.~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md._log.yaml — set last_updated to today, apply any field updates.The portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — find the row~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md — append target~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md — reference (don't rewrite)~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md — risk calibration (if re-assessing risk)Conflicts gate — unbypassable. Before logging an update, 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 exists. I won't append history to an unmanaged matter — the conflicts check is the gate, and there's nohistory.mdto append to until the matter is intaken."
Slug (required). If not provided, ask — with a short list of recently updated matters to pick from.
Offer categories:
Or freeform if none fits.
Default today. Accept an override (e.g., capturing an event from last week).
One-paragraph narrative. What happened, what it means, any immediate implication.
Walk through potentially affected fields:
status: — has the stage shifted (e.g., pleadings → fact discovery)?stage: — substage updaterisk: — reassessment required?materiality: — any change (new facts might trigger reserve or disclosure)?exposure_range: — revise if new informationnext_deadline: — new upcoming date, if anyoutside_counsel: — change?internal_owners: — anyone new or removed?legal_hold: — refreshed, expanded, released?Only prompt for fields likely affected by the event type. Procedural updates usually touch stage and next_deadline only; a settlement offer might touch materiality, exposure_range, status.
If the Strategy update is a settlement acceptance (the company is accepting a settlement offer, executing a settlement agreement, or authorizing acceptance in principle — not merely logging an offer made or received): Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md. If the Role is Non-lawyer:
Accepting a settlement has legal consequences — it resolves claims, typically requires a release, and can affect insurance, tax, and related matters. 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.