| name | matter-briefing |
| title | $litigation-legal:matter-briefing |
| description | Deep briefing on one matter — current posture, what's changed, next deadline, open questions, and a risk re-assessment check, ready before a GC update or outside counsel call. Use when the user says "brief me on [matter]", "where are we on [matter]", or needs a read on a specific matter. |
| author | alexchlou |
| author_url | https://github.com/alexchlou/codex-for-legal/tree/main/plugins/litigation-legal/skills/matter-briefing |
| 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-briefing
- Load
config/local/codex-for-legal/litigation-legal/CLAUDE.md → risk calibration + relevant stakeholders.
- Follow the workflow and reference below.
- Read
config/local/codex-for-legal/litigation-legal/matters/[slug]/matter.md + config/local/codex-for-legal/litigation-legal/matters/[slug]/history.md + log row from _log.yaml.
- Produce briefing: current posture, what's changed since last update, next deadline, open questions, risk re-assessment check ("does the
risk: field still reflect reality?").
- Flag staleness: if
last_updated > 30 days, say so.
Matter Briefing
Purpose
Give the counsel a clean read on one matter in the time it takes to walk to a conference room. Current posture, what's changed, what's next, what's worth reconsidering.
Load context
config/local/codex-for-legal/litigation-legal/matters/_log.yaml — structured rowconfig/local/codex-for-legal/litigation-legal/matters/[slug]/matter.md — narrative intakeconfig/local/codex-for-legal/litigation-legal/matters/[slug]/history.md — event logconfig/local/codex-for-legal/litigation-legal/CLAUDE.md — risk calibration (so "risk: high" means something specific, not generic)
Conflicts gate — unbypassable. Before briefing, 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. Run $litigation-legal:matter-intake first so the conflicts check runs and the matter workspace is set up. I won't build a briefing on a matter that hasn't been intaken — the conflicts check is the gate."
