matter-briefing

/matter-briefing

Load ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md → risk calibration + stakeholders.
Follow the workflow below.
Read the log lines in ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/matter.md + ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md + _log.yaml .
Generate the brief: current posture, changes since the last update, next milestone, open questions, risk recalibration check ("risk: field still reflects reality?").
Flag staleness: if last_updated > 30 days, state so explicitly.

Case Brief

Purpose

Let a lawyer read up on a case on the walk to the conference room. Current posture, what has changed, what to do next, what is worth reconsidering.

Load context

~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/_log.yaml — structured rows
~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/matter.md — narrative register
~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md — event log
~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md — risk calibration (so that "risk: high" has concrete meaning, rather than being vague)

Conflict gate — cannot be bypassed. Before generating the brief, check whether the case code exists in _log.yaml . If the case is not in _log.yaml , refuse and route:

"I did not find [case code] in the case log. Please run /litigation-legal:matter-intakefirst, so that the conflict check can run and the case workspace can be established. I will not generate a brief for an unregistered case — the conflict check is the gate."

Input

Code (required). If ambiguous or missing, ask the user to select from the active case list.

Brief content

[工作成果标头——根据插件配置 ## 输出——因角色不同；见 `## 使用者`]

# [案件名称] —— 简报（截至[今天]）

**状态：** [状态 / 阶段]
**风险：** [评级]（[严重性] × [可能性]）
**重要性：** [类别]
**外聘律师：** [律所 —— 主办律师]
**最后更新：** [日期] [⚠️ 陈旧 >30天]
**利益冲突：** [状态 —— ⚠️ 如 `待定` 或 `未运行`]

---

## 一段话概要

[当前姿态。我们在做什么、为什么。如登记时记录了关键事实，请指名。]

## 近期变化

[history.md 中最近3-5条记录，最新在前。如历史记录较薄，说明。]

## 下一步

- **临近节点：** [next_deadline + 是什么节点]
- **即将到来的里程碑：** [matter.md 或近期历史记录中的任何日期事项]
- **待决定事项：** [matter.md 中标注的待解决问题]

## 敞口

[范围 + 自登记以来的任何变化。如已计提，当前计提金额 + 是否需要重新校准。]

## 内部负责人

[已纳入的人员；是否有人应该纳入但未被纳入]

## 风险重评估检查

*提示，非答案。*

- `risk: [评级]` 是否仍感觉正确，还是案件发生了变化？
- `materiality: [类别]` 是否仍然匹配？（新事实可能推动向计提或披露变化。）
- 案件是否需要补充新的相关方（如证据开示后信息安全负责人变得相关）？

## 待解决问题

[来自 matter.md 及历史记录中尚未解决的事项]

## 通话前备忘

[如用户指定了目的——"在外部律师通话前给我简报"——定制本节：应问的问题、应获取的决定、应提取的进展。如未指定目的，省略本节。]

Staleness

If last_updated > 30天前: flag at the top and suggest running /litigation-legal:matter-update [slug] after the meeting to record what was discussed.

Tone

This is not marketing copy. State what is known; flag what is not known. If the case history is thin and it was just filed, the brief is short — that is correct. Do not pad.

End with the next-step decision tree

End with the next-step decision tree in CLAUDE.md ## 输出 . Customize the options based on what this skill just produced — the five default branches (draft X, escalate, get more facts, wait and see, other options) are a starting point, not a locked-in set. The decision tree itself is the output; the lawyer chooses.

What this skill does not do

Predict outcomes. Risk ratings are documented judgments, not predictions.
Recommend strategy. Surface questions; the lawyer answers.
Re-triage. If the user wants to re-triage, do a field change via /matter-update — this skill is read-only and does not write.