$ loading_
Close a matter — capture outcome, final exposure, and lessons, then archive it out of the active portfolio without deleting the record. Use when the user wants to close a matter, says "[matter] is done", or needs to record a settlement, dismissal, judgment, withdrawal, or consolidation outcome.
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "matter-close" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/matter-close/SKILL.md 2. 保存为 ~/.claude/skills/matter-close/SKILL.md 3. 装好后重载技能，告诉我可以用了
_log.yaml: status: closed, add closed: YYYY-MM-DD and outcome: fields.~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md._log.yaml and ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/ — not deleted. /portfolio-status filters it from active rollups.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.
~/.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 targetConflicts 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."
Slug (required).
settled — with counterparty, dollar amount, structural termsdismissed — with or without prejudice, by what mechanismjudgment-for-us — at what stage, appeal exposurejudgment-against-us — at what stage, appeal status, exposure crystallizedwithdrawn — by counterparty, circumstancesconsolidated — merged into another matter (provide slug of parent)other — with explanationThe date the matter actually ended (settlement executed, order issued, dismissal filed).
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."
Settlement agreement, final order, dismissal — path if available. Not required.
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 --releaseseparately 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.]
…
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.