Back to Details

matter-update

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/matter-update

/matter-update

  1. Follow the workflow and reference below.
  2. Confirm slug exists in 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/
    and 
    _log.yaml
    .
  3. Prompt for event type, date (default today), summary, and any log field updates (risk change, status change, next deadline shift, materiality reclassification).
  4. Append dated entry to 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    .
  5. Update 
    _log.yaml
    — set 
    last_updated
    to today, apply any field updates.
  6. Confirm.
  1. 遵循以下工作流程和参考内容。
  2. 确认slug存在于
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/
    和
    _log.yaml
    中。
  3. 提示用户输入事件类型、日期（默认当天）、摘要以及任何日志字段更新（风险变更、状态变更、下一个截止日期调整、重要性重新分类）。
  4. 将带日期的条目追加到
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    。
  5. 更新
    _log.yaml
    ——将
    last_updated
    设置为当天，应用所有字段更新。
  6. 确认操作。

Matter Update

事务更新

Purpose

目的

The portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.
投资组合只有保持最新状态才有用。本技能让记录更新变得简单——只需两分钟的结构化记录，无需自由格式的零散内容。

Load context

加载上下文

  • ~/.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-intake
first 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 no 
history.md
to append to until the matter is intaken."
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    ——查找对应行
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    ——追加目标文件
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md
    ——参考文件（请勿改写）
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
    ——风险校准（如果重新评估风险）
冲突检查门——不可绕过。在记录更新前，检查
_log.yaml
中的事务slug。如果事务不在
_log.yaml
中，拒绝操作并引导：
“我在事务日志中未找到[事务slug]。请先运行
/litigation-legal:matter-intake
，以便执行冲突检查并创建事务工作区。我不会向未管理的事务追加历史记录——冲突检查是必经流程，事务被纳入管理前不存在可追加的
history.md
文件。”

Input

输入

Slug (required). If not provided, ask — with a short list of recently updated matters to pick from.
Slug（必填）。如果未提供，询问用户——并提供最近更新的事务短列表供选择。

The update

更新步骤

1. Event type

1. 事件类型

Offer categories:
  • Procedural — motion filed/received, order issued, hearing held, deadline set
  • Discovery — production made/received, depositions taken, subpoena served
  • Substantive — new facts, key document surfaced, ruling on merits
  • Strategy — posture shift, settlement offer made/received, authority update
  • Risk re-assessment — severity or likelihood changed
  • Stakeholder — new person looped in, outside counsel change
  • Administrative — engagement letter executed, budget adjusted, hold refreshed
Or freeform if none fits.
提供以下分类：
  • 程序类——提交/收到动议、发布命令、举行听证会、设定截止日期
  • 取证类——提交/收到证据、进行证词取证、送达传票
  • 实体类——新事实、关键文件浮出水面、实体裁决
  • 策略类——立场转变、提出/收到和解提议、权限更新
  • 风险重新评估——严重程度或可能性变更
  • 利益相关方——新增人员参与、外部律师变更
  • 行政类——签署委托函、调整预算、更新保留通知
如果以上分类均不适用，可接受自由输入。

2. Date

2. 日期

Default today. Accept an override (e.g., capturing an event from last week).
默认当天。接受自定义日期（例如，记录上周的事件）。

3. Summary

3. 摘要

One-paragraph narrative. What happened, what it means, any immediate implication.
一段式叙述。说明发生了什么、意味着什么以及任何直接影响。

4. Log field changes

4. 日志字段变更

Walk through potentially affected fields:
  • status:
    — has the stage shifted (e.g., pleadings → fact discovery)?
  • stage:
    — substage update
  • risk:
    — reassessment required?
  • materiality:
    — any change (new facts might trigger reserve or disclosure)?
  • exposure_range:
    — revise if new information
  • next_deadline:
    — new upcoming date, if any
  • outside_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
.
逐一梳理可能受影响的字段：
  • status:
    ——阶段是否变更（例如，诉答程序→事实取证）？
  • stage:
    ——子阶段更新
  • risk:
    ——是否需要重新评估？
  • materiality:
    ——是否有变更（新事实可能触发准备金或披露要求）？
  • exposure_range:
    ——如有新信息则修订
  • next_deadline:
    ——如有新的即将到来的日期
  • outside_counsel:
    ——是否变更？
  • internal_owners:
    ——是否有新增或移除人员？
  • legal_hold:
    ——是否更新、扩大或解除？
仅针对可能受事件类型影响的字段进行提示。程序类更新通常仅涉及
stage
和
next_deadline
；和解提议可能涉及
materiality
、
exposure_range
、
status
。

4pre. Settlement-acceptance gate

4pre. 和解接受检查门

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:
[Generate a 1-page summary: the matter, proposed settlement terms (dollar, structural, release scope, confidentiality, non-disparagement), exposure at stake, authority ladder status (see 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
settlement authority), what could go wrong, what to ask the attorney before accepting.]
If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA/Bar Standards Board in England & Wales, Law Society in Scotland/NI/Ireland/Canada/Australia, or your jurisdiction's equivalent).
Do not log the acceptance or flip materiality on acceptance basis without an explicit yes. Logging offers or counters does not require the gate — acceptance does.
如果策略类更新是接受和解（公司接受和解提议、签署和解协议或原则上授权接受——不仅仅是记录提出或收到的提议）：阅读
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的
## Who's using this
部分。如果角色是非律师：
接受和解会产生法律后果——它会解决索赔，通常要求签署免责声明，并可能影响保险、税务及相关事务。您是否已与律师讨论过此事？如果是，请继续。如果否，以下是一份提交给律师的简要说明：
[生成1页摘要：事务情况、拟议和解条款（金额、结构、免责范围、保密条款、非贬低条款）、涉及的风险敞口、权限层级状态（参见
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的和解权限）、可能出现的问题、接受前应向律师询问的事项。]
如果您需要在所在辖区寻找持牌律师、事务律师、出庭律师或其他授权法律专业人士：您所在行业监管机构的推荐服务是最快的起点（美国为州律师协会，英格兰和威尔士为SRA/律师标准委员会，苏格兰/北爱尔兰/爱尔兰/加拿大/澳大利亚为律师协会，或您所在辖区的等效机构）。
在未得到明确同意的情况下，不得记录接受和解或基于接受变更重要性。记录提议或反提议无需经过此检查门——只有接受需要。

4a. Materiality trigger — explicit prompt

4a. 重要性触发——明确提示

Certain event types force a materiality re-check. When the event type is in this list, always prompt — don't let the user move on without an explicit answer:
Event typeMateriality trigger prompt
Substantive (new facts, key document, merits ruling)"This event is substantive. Does it push 
materiality
? Current: 
[current]
. Options: 
reserved / disclosed / monitored / none
. Change?"
Strategy (posture shift, settlement offer made or received)"Settlement activity often triggers materiality reclassification. Current: 
[current]
. If the offer, counter, or acceptance moves exposure or shifts from contested to probable-and-estimable, reclassify."
Risk re-assessment (severity or likelihood changed)"Risk moved. Materiality should track. Current: 
[current]
. Reclassify?"
Regulatory / enforcement development"Regulator action (subpoena, CID, enforcement notice) usually triggers disclosure analysis. Current: 
[current]
. Change?"
Acceptable answers include 
no change
— but 
no change
must be explicit, not implied by silence. Capture in the history entry:
markdown
**Materiality check:** [no change / changed from X to Y]
**Reasoning:** [one sentence]
If materiality moves to 
reserved
or 
disclosed
, and the matter did not previously carry a reserve or disclosure, flag the event as requiring finance / audit-committee notification per 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
materiality thresholds.
某些事件类型必须重新检查重要性。当事件类型属于以下列表时，必须提示——用户必须给出明确答案才能继续：
事件类型重要性触发提示
实体类（新事实、关键文件、实体裁决）“此事件属于实体类。是否会改变
materiality
？当前值：
[current]
。选项：
reserved / disclosed / monitored / none
。是否变更？”
策略类（立场转变、提出或收到和解提议）“和解活动通常会触发重要性重新分类。当前值：
[current]
。如果提议、反提议或接受变更了风险敞口，或从有争议变为可能且可估算，请重新分类。”
风险重新评估（严重程度或可能性变更）“风险已变更。重要性应随之调整。当前值：
[current]
。是否重新分类？”
监管/执法进展“监管机构行动（传票、CID、执法通知）通常会触发披露分析。当前值：
[current]
。是否变更？”
可接受的答案包括
no change
——但
no change
必须是明确回答，而非默认沉默。在历史条目中记录：
markdown
**重要性检查：** [无变更 / 从X变更为Y]
**理由：** [一句话说明]
如果重要性变为
reserved
或
disclosed
，且该事务此前未计提准备金或进行披露，则根据
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的重要性阈值，标记该事件为需要通知财务/审计委员会。

5. Seed doc prompt (optional)

5. 种子文档提示（可选）

If the update references a document (order, filing, correspondence), ask if there's a path to link. Not pushy.
如果更新涉及某份文件（命令、诉状、信函），询问用户是否有文件路径可链接。无需强制要求。

Writing

撰写规则

Append to 
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md

追加到
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md

Most recent at top, directly under the 
---
that follows the header.
markdown
undefined
最新条目放在最顶部，紧跟标题后的
---
下方。
markdown
undefined

[YYYY-MM-DD] — [Event type]: [short title]

[YYYY-MM-DD] — [事件类型]: [简短标题]

[Paragraph summary.]
Fields changed:
  • [field]: [old → new]
  • [field]: [old → new]
Related doc: [path, if provided]

If no fields changed, omit the "Fields changed" block.
[段落摘要。]
变更的字段：
  • [字段]: [旧值 → 新值]
  • [字段]: [旧值 → 新值]
相关文档： [路径（如果提供）]

如果没有字段变更，省略“变更的字段”模块。

Update 
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml

更新
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml

  • Apply any field changes.
  • Set 
    last_updated: [today]
    (or the event date if the user overrode — the log tracks when the record was last touched).
  • 应用所有字段变更。
  • 设置
    last_updated: [today]
    （如果用户自定义了日期，则使用事件日期——日志记录的是记录最后被修改的时间）。

Confirm

确认

Show the user the history entry and the yaml diff before writing:
Here's what I'll append and update. Good to commit?
在写入前向用户展示历史条目和yaml差异：
以下是我将追加和更新的内容。是否确认提交？

What this skill does not do

本技能不执行的操作

  • Edit past history entries. Corrections are new entries that reference and correct prior ones.
  • Silently change the log. Every field change is shown to the user before write.
  • Decide whether a new development warrants reserve/disclosure. It surfaces the question ("this might push materiality — want to reclassify?"), the user answers.
  • 编辑过往历史条目。更正需通过新增条目并引用和修正之前的条目来完成。
  • 静默修改日志。所有字段变更在写入前都会展示给用户。
  • 决定新进展是否需要计提准备金/披露。它只会提出问题（“这可能会改变重要性——是否要重新分类？”），由用户回答。