| name | matter-briefing-anthropics |
| title | /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 | anthropics |
| author_url | https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/matter-briefing |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | litigation |
| language | en |
/matter-briefing
- Load
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → risk calibration + relevant stakeholders.
- Follow the workflow and reference below.
- Read
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md + ~/.claude/plugins/config/claude-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
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — structured row~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md — narrative intake~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md — event log~/.claude/plugins/config/claude-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."
Input
Slug (required). If ambiguous or missing, ask the user to pick from a list of active matters.
The briefing
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
# [Matter Name] — Briefing as of [today]
**Status:** [status / stage]
**Risk:** [rating] ([severity] × [likelihood])
**Materiality:** [category]
[firm — lead]
[date] [flag ⚠️ STALE if >30d]
[status — flag ⚠️ if or ]
---
[Current posture. What are we doing and why. Name the pivot fact if one is captured.]
[Last 3-5 entries from history.md, most recent first. If history is thin, say so.]
[next
