Skip to content
cccskills
Official · ClaudeFreePublished on GitHub

matter-close

Record how a legal matter ended, its final cost, differences from the original risk estimate, and lessons learned. Close active tracking while preserving the matter’s files and history for future reference.

OriginalShow the original description

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.

Run score Not tested

See how to install

Good for

  • Recording a settlement or judgment
  • Comparing final costs with initial estimates
  • Preserving lessons from a completed matter
  • Removing closed matters from active summaries

Files included (1)

  • SKILL.md6.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/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.

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."

Input

Slug (required).

The close

1. Resolution type

  • 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

2. Resolution date

The date the matter actually ended (settlement executed, order issued, dismissal filed).

3. Final exposure

  • 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

4. Lessons

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."

5. Seed doc prompt

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.

Update ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.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.

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

## [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]

Touch ~/.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):

---

## Closed [YYYY-MM-DD]

[Resolution summary in one paragraph. Pointer to the final history entry for detail.]

Confirm

Show the user the full close entry and the yaml changes before writing.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ai-inventory

Official · ClaudeFreeSummary

Build an AI system register for EU AI Act reviews. Track owners, deployment status, EU connections, and each system’s role and risk category through a guided discussion, preserving classification reasons and dates for future review.

  • Register AI systems used or planned across an organization
  • Review each system’s role and risk category
  • Find systems approaching their next review date
anthropics/claude-for-legal9.8KUpdated Oct 22, 2026

ai-tool-handoff

Official · ClaudeFreeSummary

Coordinate bulk contract clause extraction with Luminance or Kira, prepare loading requests, and check returned results according to your team's review settings. Assess flagged clauses against the transaction and organize findings and required consents.

  • Preparing bulk clause extraction requests for contract batches
  • Sampling AI extraction results against original clauses
  • Checking whether change-of-control clauses apply to a deal
anthropics/claude-for-legal9.8KUpdated Oct 22, 2026

aia-generation

Official · ClaudeFreeSummary

Create an AI impact assessment in your team's format. Gather system details through conversation, analyze risks and applicable regulatory classifications, check consistency with internal policy, and document recommendations, safeguards, and conditions for deployment.

  • Assessing an AI system before deployment
  • Preparing an assessment after conditional triage
  • Reviewing pilot or production AI risks
anthropics/claude-for-legal9.8KUpdated Oct 22, 2026

amendment-history

Official · ClaudeFreeSummary

Trace changes across an original contract and its amendments. Get a chronological overview or follow one clause through successive revisions, with section references, current wording, and flags for conflicting or unclear language that needs legal review.

  • Summarize a contract’s amendment history
  • Find the current wording of a specific clause
  • Track changes to fees or liability limits
anthropics/claude-for-legal9.8KUpdated Oct 22, 2026

auto-updater

Official · ClaudeFreeSummary

Check installed community skills for updates, review file changes and expanded permissions, and flag outdated references. Updates require explicit approval, with backups available to restore the previous version if needed.

  • Check installed skills for available updates
  • Review permission changes before updating
  • Identify references overdue for verification
anthropics/claude-for-legal9.8KUpdated Oct 22, 2026

bar-prep-questions

Official · ClaudeFreeSummary

Practice for a U.S. bar exam with questions matched to the exam format, jurisdiction, and weak subjects. Get explanations for answer choices, essay feedback, and session records that reveal recurring mistakes and guide further practice.

  • Drilling weak subjects for a specific bar exam
  • Comparing general rules with state-specific rules
  • Getting feedback on practice essays
anthropics/claude-for-legal9.8KUpdated Oct 22, 2026

See all skills by anthropics

Report a problem with this skill