| name | matter-close |
| title | $litigation-legal:matter-close |
| 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. |
| author | alexchlou |
| author_url | https://github.com/alexchlou/codex-for-legal/tree/main/plugins/litigation-legal/skills/matter-close |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | litigation |
| language | en |
Codex v1 local-input note: This migrated skill supports local files and pasted text by default. References to Drive, CLM IDs, Slack, Westlaw, iManage, Ironclad, eDiscovery, dockets, or other remote systems require a separately configured Codex connector/MCP server. When a connector is unavailable, ask for a local export, local file path, or pasted excerpts. If config/local/codex-for-legal/<practice>/CLAUDE.md is missing, ask the user to run the relevant cold-start-interview or customize skill and copy from config/templates/codex-for-legal/<practice>/CLAUDE.md.
$litigation-legal:matter-close
- Follow the workflow and reference below.
- Confirm slug and current status.
- Capture outcome: resolution type (settled, dismissed, judgment for/against, withdrawn, consolidated), date, final exposure/cost, lessons.
- Update
_log.yaml: status: closed, add closed: YYYY-MM-DD and outcome: fields.
- Append final entry to
config/local/codex-for-legal/litigation-legal/matters/[slug]/history.md.
- Matter stays in
_log.yaml and config/local/codex-for-legal/litigation-legal/matters/[slug]/ — not deleted. $litigation-legal: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
config/local/codex-for-legal/litigation-legal/matters/_log.yaml — find the rowconfig/local/codex-for-legal/litigation-legal/matters/[slug]/matter.md — reference (intake context)config/local/codex-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."
