SuperAPI AI Directory

matter-close

Office & productivity

View repository

Updated 10-15 20:29

About this skill

/matter-close
  1. Operate according to the following workflow.
  2. Confirm the code name and current status.
  3. Capture the outcome: closing type (settlement, dismissal, judgment in our favor/against us, withdrawal, consolidation), date, final exposure/cost, lessons learned.
  4. Update _log.yaml:status: closed, add closed: YYYY-MM-DD and outcome: fields.
  5. Append the final entry to ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md .
  6. The case remains in _log.yaml and ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/ — do not delete./portfolio-status Filter from the active summary.

Case Closed

Purpose

Cases end. The outcome is the most valuable data point the case portfolio generates — it calibrates the risk framework for future cases. Closing a case captures the outcome in a structured way so the record is useful, not merely archived.

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]/matter.md — reference (context at registration)
  • ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md — append target

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

"I did not find [case code name] in the case log. There is no case to close — either the code name is wrong, or the case was never registered through /litigation-legal:matter-intake . Please check the code name first; if it was indeed never registered, then there is no row to update and no file structure to close."

Input

Code name (required).

Closing content

1. Closing type

  • 和解 — settlement reached with the opposing party, including amount and structural terms
  • 撤诉 — the opposing party withdraws the claim / we withdraw the claim
  • 判决我方胜诉 — at what stage, appeal risk
  • 判决我方败诉 — at what stage, appeal status, exposure determined
  • 撤回 — withdrawn by the opposing party, with a description of the circumstances
  • 合并 — merged into another case (provide the parent case code name)
  • 其他 — with explanation

2. Closing date

The date the case actually ended (settlement agreement signed, ruling issued, dismissal filed).

3. Final exposure

  • The company's actual cost (settlement amount + attorney fees + injunction/structural costs)
  • vs. the initial exposure range at registration (was our prediction accurate?)
  • Provision accuracy (if any provision): book vs. actual

4. Lessons learned

Two to three sentences. What did we judge correctly? What did we misjudge? What should have been flagged earlier at registration?

This is the part future lawyers will reread. Be honest. "Misjudged the likelihood — the plaintiff was more aggressive than expected" is more valuable than "the outcome was favorable to us."

5. Document link hints

Settlement agreement, final ruling, dismissal ruling — with paths if available. Not required.

Write

Before closing the case (the act that has consequences — the case is archived and stops being actively tracked): Read ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md in ## 使用者. If the role isnon-lawyer:

Closing a case has legal consequences—it ends active tracking, may affect associated evidence preservation (if applicable, run separately /legal-hold --release), and establishes the final record the company relies on. Have you reviewed this matter with a lawyer? If so, proceed. If not, here is a brief to take to a lawyer:

[Generate a one-page summary: the case, closure type and terms, final exposure vs. initial, accrual accuracy, whether related cases or appeals are still ongoing, what could go wrong with an early closure, questions to ask the lawyer.]

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

Do not write the closure fields or append the closure entry until explicit confirmation is received.

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

status: closed
closed: [YYYY-MM-DD]
outcome: [结案类型]
final_cost: [金额]
last_updated: [今天]   # 结案是最后的触及;记录它

Keep all existing fields. Do not delete log lines.

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

## [YYYY-MM-DD] —— 案件结案:[结案类型]

**结果:** [叙述——发生了什么、以什么条件]
**最终成本:** [金额 + 如有结构条款]
**vs. 初始敞口:** [对比 matter.md 登记范围]
**计提准确性:** [如适用]

**反思教训:**
[2-3句话——诚实的回顾]

**关联文件:** [和解协议 / 终局裁定 / 等,如有提供]

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

Add a closure block at the end (do not modify the preceding sections—they are historical registration records):

---

## 结案于 [YYYY-MM-DD]

[结果摘要,一段。指向最终历史条目获取详情。]

Confirm

Show the user the complete closure entry and yaml changes before writing.

What this skill does not do

  • Delete cases. Closed cases remain in _log.yaml and on disk—they are the training set for case portfolio judgment.
  • Reopen cases. If a closed case resurfaces (appeal, related litigation), open a new case and reference the closed case in matter.md .
  • Summarize lessons the user did not mention. If the user skips the lessons section, leave it blank rather than fabricating.