SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsmatter-update

matter-update

General & other

View repository

Updated 10-15 20:30

About this skill

/matter-update
  1. Operate according to the following workflow.
  2. Confirm the code exists in ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/ and _log.yaml .
  3. Prompt for input: event type, date (default today), summary, and any log field updates (risk change, status change, next milestone change, materiality reclassification).
  4. Append a dated entry to ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md。
  5. Update _log.yaml —— last_updated set to today, apply any field updates.
  6. Confirm.
Case Update

Purpose

A case portfolio is only useful if it stays up to date. This skill makes recording updates easy — two minutes of structured logging, no drift.

Load context

  • ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/_log.yaml — find the corresponding row
  • ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md — append target
  • ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/matter.md — reference (do not rewrite)
  • ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md — risk calibration (if risk needs reassessment)

Conflict gate — cannot be bypassed. Before recording an update, check whether the case code exists in _log.yaml . If the case is not in _log.yaml , refuse and route:

"I did not find [case code] in the case log. Please run /litigation-legal:matter-intakefirst, so that the conflict check can run and the case workspace is established. I will not append history to an unregistered case — the conflict check is the gate, and before the case is registered there is no history.md available to append to."

Input

Code (required). If not provided, ask — with a short list of recently updated cases to choose from.

Update content

1. Event type

Provide categories:

  • Procedural — complaint/answer/motion filed or received, ruling/judgment issued, hearing/pretrial conference held, deadline set
  • Evidentiary — evidence submitted or received, witness appearance/examination conducted, subpoena served
  • Substantive — new facts, key document surfaced, substantive ruling
  • Strategy — posture shift, settlement offer sent or received, authority update
  • Risk reassessment — severity or likelihood change
  • Parties — new personnel added, outside counsel change
  • Administrative — engagement letter signed, budget adjustment, litigation hold refreshed

If none of the above match, use free form.

2. Date

Default today. Override acceptable (e.g., recording last week's event).

3. Summary

One-paragraph narrative. What happened, what it means, any immediate impact.

4. Log field changes

Check each field that may be affected:

  • status: — has the stage shifted (e.g., filing → trial)?
  • stage: — substage update
  • risk: — is reassessment needed?
  • materiality: — has there been a change?
  • exposure_range: — correct if new information emerges
  • next_deadline: — new upcoming dates (if any)
  • outside_counsel: — Change?
  • internal_owners: — Personnel added or removed?
  • legal_hold: — Refreshed, expanded, or lifted?

Prompt only for fields that the event type may affect. Procedural updates typically involve only stage and next_deadline; settlement offers may involve materiality、exposure_range、status。

4pre. Settlement Acceptance Gate

If the policy update isaccept settlement(the company is accepting a settlement offer, signing a settlement agreement, or authorizing acceptance in principle—not merely recording that an offer was made or received): read ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md in ## 使用者. If the role isnon-lawyer：

Accepting a settlement has legal consequences—it resolves the dispute, usually requires signing a release, and may affect insurance, taxes, and related matters. Have you reviewed this with a lawyer? If so, continue. If not, here is a brief to take to a lawyer:

[Generate a one-page summary: the case, the proposed settlement terms (amount, structure, scope of release, confidentiality, non-disparagement clauses), the exposure involved, the status of authorization levels (see ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md settlement authority), what could go wrong, and questions to ask a lawyer before accepting.]

If you need to find a lawyer: contact your local bar association or call the 12348 legal aid hotline for a referral.

Do not record acceptance or flip materiality until explicit confirmation is received. Recording an offer or counteroffer does not require a gate—acceptance does.

4a. Materiality Triggers—Explicit Prompts

Certain event types force a materiality recheck. When the event type is in the following list,always prompt—do not let the user skip without an explicit answer:

Event Type Materiality Trigger Prompt
Substantive (new facts, key documents, entity ruling) "This event is substantive. Does it drive materiality? Current:[current]. Options:需计提 / 已披露 / 监控中 / 不适用. Change?"
Strategy (posture shift, settlement offer made or received) "Settlement activity often triggers materiality reclassification. Current:[current]. If an offer, counteroffer, or acceptance changes the exposure or shifts it from disputed to probable and estimable, reclassify."
Risk reassessment (severity or likelihood change) "The risk has changed. Materiality should follow. Current:[current]. Reclassify?"
Administrative regulatory / enforcement developments "Regulatory action (cooperation notice, enforcement notice) often triggers disclosure analysis. Current:[current]. Change?"

An acceptable answer includes "no change"—but "no change" must be explicit and cannot be implied by silence. Capture it in the history:

**重要性检查：** [未变更 / 从 X 变更为 Y]
**理由：** [一句话]

If materiality changes to "accrual required" or "disclosed," and the case has not previously recorded an accrual or disclosure, flag that the event requires notifying the finance/audit committee under the ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md materiality threshold.

5. Document Linking Prompt (Optional)

If the update references a document (ruling, complaint, correspondence), ask whether there is a path link. Not required.

Write

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

Newest record first, placed directly after the header under --- .

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

[段落摘要。]

**字段变更：**
- [字段]: [旧 → 新]
- [字段]: [旧 → 新]

**关联文件：** [路径，如有提供]

If there are no field changes, omit the "field changes" block.

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

  • Apply any field changes.
  • Set last_updated: [今天](if the user overrides the date, use the event date — the log records the time the record was last touched).

Confirm

Before writing, show the user the history entries and the yaml diff:

This is what I will append and update. May I write it?

What this skill does not do

  • Edit past history log entries. A correction is a new entry that references and corrects a past entry.
  • Silently change the log. Every field change is shown to the user before writing.
  • Decide whether a new development requires accrual/disclosure. Surface the question ("this might drive materiality — does it need to be reclassified?"), and the user answers.