Back to Details

matter-close

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/matter-close

/matter-close

  1. Follow the workflow and reference below.
  2. Confirm slug and current status.
  3. Capture outcome: resolution type (settled, dismissed, judgment for/against, withdrawn, consolidated), date, final exposure/cost, lessons.
  4. Update 
    _log.yaml
    : 
    status: closed
    , add 
    closed: YYYY-MM-DD
    and 
    outcome:
    fields.
  5. Append final entry to 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    .
  6. Matter stays in 
    _log.yaml
    and 
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/
    — not deleted. 
    /portfolio-status
    filters it from active rollups.
  1. 遵循以下工作流程和参考内容。
  2. 确认slug和当前状态。
  3. 记录结果：解决类型（settled、dismissed、judgment-for-us/judgment-against-us、withdrawn、consolidated）、日期、最终风险敞口/成本、经验教训。
  4. 更新
    _log.yaml
    ：设置
    status: closed
    ，添加
    closed: YYYY-MM-DD
    和
    outcome:
    字段。
  5. 在
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    中追加最终条目。
  6. 事务保留在
    _log.yaml
    和
    ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/
    中——不会被删除。
    /portfolio-status
    会将其从活跃汇总中过滤掉。

Matter Close

Matter Close

Purpose

目的

Matters end. The outcome is the single most valuable data point the portfolio generates — it calibrates the risk framework for future matters. Closing a matter captures the outcome structurally so the record is useful, not just archived.
事务会结束。结果是项目组合产生的最有价值的数据点——它为未来的事务校准风险框架。关闭事务会结构化地记录结果，使记录有用而非仅被归档。

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]/matter.md
    — reference (intake context)
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    — append target
Conflicts gate — unbypassable. Before closing, 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. Nothing to close — either the slug is wrong or the matter was never intaken through 
/litigation-legal:matter-intake
. Check the slug first; if it genuinely was never intaken, there's no row to update and no file structure to close."
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
    — 查找对应行
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md
    — 参考内容（录入上下文）
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
    — 追加目标文件
冲突检查——不可绕过。 关闭前，检查
_log.yaml
中的事务slug。如果事务不在
_log.yaml
中，拒绝操作并引导：
"我在事务日志中未找到[事务slug]。无可关闭内容——要么slug错误，要么事务从未通过
/litigation-legal:matter-intake
录入。请先检查slug；如果确实从未录入，则没有可更新的行和可关闭的文件结构。"

Input

输入

Slug (required).
Slug（必填）。

The close

关闭操作

1. Resolution type

1. 解决类型

  • settled
    — with counterparty, dollar amount, structural terms
  • dismissed
    — with or without prejudice, by what mechanism
  • judgment-for-us
    — at what stage, appeal exposure
  • judgment-against-us
    — at what stage, appeal status, exposure crystallized
  • withdrawn
    — by counterparty, circumstances
  • consolidated
    — merged into another matter (provide slug of parent)
  • other
    — with explanation
  • settled
    — 与对方达成和解，涉及金额、结构性条款
  • dismissed
    — 有或无prejudice，通过何种机制
  • judgment-for-us
    — 处于哪个阶段，上诉风险
  • judgment-against-us
    — 处于哪个阶段，上诉状态，已明确的风险敞口
  • withdrawn
    — 由对方撤诉，相关情况
  • consolidated
    — 合并到另一事务中（提供父事务的slug）
  • other
    — 附解释

2. Resolution date

2. 解决日期

The date the matter actually ended (settlement executed, order issued, dismissal filed).
事务实际结束的日期（和解协议签署、命令下达、驳回申请提交）。

3. Final exposure

3. 最终风险敞口

  • Actual cost to company (settlement amount + fees + injunctive/structural cost)
  • vs. initial exposure range at intake (did we call it?)
  • Reserve accuracy (if reserved): booked vs. actual
  • 公司实际成本（和解金额+费用+禁令/结构性成本）
  • 与录入时的初始风险敞口范围对比（我们是否预判准确？）
  • 准备金准确性（若已计提）：账面金额vs实际金额

4. Lessons

4. 经验教训

Two or three sentences. What did we get right? What did we misjudge? Anything the intake should have flagged earlier?
This is the part future counsel will reread. Be honest. "Misjudged likelihood — plaintiff firm was more aggressive than expected" is worth more than "resolved favorably."
2-3句话。我们做对了什么？误判了什么？录入阶段本应更早标记的内容？ 这部分是未来法律顾问会重读的内容。请如实填写。“误判可能性——原告律所比预期更激进”比“顺利解决”更有价值。

5. Seed doc prompt

5. 原始文档提示

Settlement agreement, final order, dismissal — path if available. Not required.
和解协议、最终命令、驳回文件——如有提供路径。非必填。

Writing

记录操作

Before closing the matter (the consequential act — the matter is archived and active tracking ends): Read 
## Who's using this
in 
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
. If the Role is Non-lawyer:
Closing a matter has legal consequences — it ends active tracking, may affect any associated legal hold (run 
/legal-hold --release
separately if appropriate), and establishes the final record the company relies on. 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, resolution type and terms, final exposure vs. initial, reserve accuracy, related matters or appeals still live, what could go wrong with premature closure, what to ask the attorney.]
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 write the close fields or append the close entry without an explicit yes.
在关闭事务前（这是具有影响的操作——事务将被归档，活跃跟踪结束）： 阅读
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md
中的
## Who's using this
部分。如果角色为非律师：
关闭事务具有法律后果——它会结束活跃跟踪，可能影响任何相关的法律保留（如有必要，请单独运行
/legal-hold --release
），并确立公司依赖的最终记录。您是否已与律师审核过此事？如果是，请继续。如果否，这里有一份提交给律师的摘要：
[生成1页摘要：事务情况、解决类型及条款、最终风险敞口与初始对比、准备金准确性、仍在进行的相关事务或上诉、过早关闭可能出现的问题、需向律师询问的内容。]
如果您需要在所在辖区寻找持牌律师、事务律师、出庭律师或其他授权法律专业人士：您所在辖区的专业监管机构推荐服务是最快的起点（美国为州律师协会，英格兰和威尔士为SRA/律师标准委员会，苏格兰/北爱尔兰/爱尔兰/加拿大/澳大利亚为律师协会，或您所在辖区的对应机构）。
未得到明确同意前，请勿填写关闭字段或追加关闭条目。

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

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

yaml
status: closed
closed: [YYYY-MM-DD]
outcome: [resolution-type]
final_cost: [dollar amount]
last_updated: [today]   # close is the last touch; record it
Retain all existing fields. Do not delete the row.
yaml
status: closed
closed: [YYYY-MM-DD]
outcome: [resolution-type]
final_cost: [dollar amount]
last_updated: [today]   # close is the last touch; record it
保留所有现有字段，请勿删除该行。

Append final entry 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
中追加最终条目

markdown
undefined
markdown
undefined

[YYYY-MM-DD] — Matter closed: [resolution-type]

[YYYY-MM-DD] — Matter closed: [resolution-type]

Resolution: [narrative — what happened, on what terms] Final cost: [amount + structural terms if any] vs. initial exposure: [compare to matter.md intake range] Reserve accuracy: [if applicable]
Lessons: [2-3 sentences — honest retrospective]
Related doc: [settlement agreement / final order / etc., if provided]
undefined
Resolution: [叙述——发生了什么，条款是什么] Final cost: [金额+如有结构性条款] vs. initial exposure: [与matter.md录入时的范围对比] Reserve accuracy: [如适用]
Lessons: [2-3句话——如实回顾]
Related doc: [和解协议/最终命令等，如有提供]
undefined

Touch 
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md

修改
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md

Add a closing block at the end (don't modify earlier sections — they're the historical intake):
markdown
---
在末尾添加关闭块（请勿修改之前的章节——它们是历史录入内容）：
markdown
---

Closed [YYYY-MM-DD]

Closed [YYYY-MM-DD]

[Resolution summary in one paragraph. Pointer to the final history entry for detail.]
undefined
[一段解决摘要。指向最终历史条目查看详情。]
undefined

Confirm

确认

Show the user the full close entry and the yaml changes before writing.
在写入前向用户展示完整的关闭条目和yaml修改内容。

What this skill does not do

本技能不执行的操作

  • Delete matters. Closed matters stay in 
    _log.yaml
    and on disk — they're the training set for the portfolio's judgment.
  • Re-open. If a closed matter comes back (appeal, related litigation), open a new matter that references the closed one in 
    matter.md
    .
  • Summarize lessons the user didn't say. If the user skips the lessons section, leave it empty rather than invent.
  • 删除事务。已关闭的事务保留在
    _log.yaml
    和磁盘中——它们是项目组合判断的训练数据集。
  • 重新开启事务。如果已关闭的事务重新出现（上诉、相关诉讼），请开启一个新事务，并在
    matter.md
    中引用已关闭的事务。
  • 总结用户未提及的经验教训。如果用户跳过经验教训部分，请留空而非编造内容。