matter-intake

/matter-intake

1. Load ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md → risk calibration (for triage), practice background (for context, conflict check methodology), related parties (for cc recipients).
2. Operate according to the following workflow.
3. Run the unified intake: identifying information, conflict check, source, risk triage, materiality, outside counsel, internal owner, evidence preservation, key dates, initial posture.
4. Generate a code name from the case name (lowercase, hyphens, year).
5. Create ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/matter.md — full narrative intake.
6. Create ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md — with this intake as the first record.
7. Append a structured row to ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/_log.yaml。
8. Confirm with the user: "This is the row I will write — any changes?"

---

Case Registration

Purpose

Every new case is registered uniformly, ensuring the case portfolio is comparable._log.yaml The uniform rows in allow the portfolio status skill to aggregate.matter.md The narrative in captures what the row format cannot express. The history file seeded here becomes the event record.

Load Context

• ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md — risk calibration (triage thresholds, materiality, settlement ladder), practice background (related parties, outside counsel roster).
• ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/_log.yaml — confirm code name uniqueness.

Intake Content

1. Identifying Information

• Case name (common reference, e.g. "XX Company v. Us 2026 Contract Dispute Case")
• Opposing party
• Case category:合同纠纷 | 劳动争议 | 知识产权 | 行政监管 | 内部调查 | 产品责任 | 其他
• Cause of action (per the Supreme People's Court's Provisions on Causes of Action for Civil Cases)[法条原文]
• Our position:原告 | 被告 | 申请人 | 被申请人 | 被调查人
  • If the practice profile's default role is already set, prefill accordingly and confirm. If the default role is "varies by case", ask directly.
• Jurisdiction (court of acceptance, arbitration institution, or administrative agency)

2. Conflict Check

Before proceeding further, run the conflict check step per ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md → conflict review.

• Status: 已通过 | 待定 | 未运行 | 已豁免
• Method: matches the method declared in ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md .
• Reviewer: name/team/firm
• Review date: YYYY-MM-DD
• Subjects reviewed: briefly list the specific names/entities actually run (opposing party, known affiliates, opposing counsel (if known), key witnesses). A small number is fine; "none" is not.
• Notes: any flagged but cleared items.

Behavior for each status:

• 已通过 → continue.

• 待定 → continue registration; prominently flag in matter.md and the log row that the conflict is unresolved; prompt again in each /matter-update and /portfolio-status until resolved.

• 已豁免 → rare; requires a conflict waiver basis (drafting the waiver is beyond this skill — record its existence, signatory, and storage location).

• 未运行 → Stop. This is a gate. Do not create until the conflict posture is resolved. matter.md、history.md or _log.yaml entry. Three acceptable paths:

  Path 1 — Run the conflict search now. Pause this registration. Follow ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md 's conflict review. On return, bring status: cleared or status: waived with reasons.

  Path 2 — Mark as pending, with owner + deadline. Available only when ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md 's conflict review statement permits parallel registration. Record: who is running the conflict search, when they are expected to return, and which entities are being checked. The registration continues; the matter row carries conflicts.status: pending；/portfolio-status marked on every run;/matter-update repeats the prompt until resolved.

  Path 3 — Bypass with written reasons. Available only when the user explicitly confirms the bypass. Record in conflicts.override :

  conflicts:
    status: not-run
    override:
      by: [用户名]
      date: [YYYY-MM-DD]
      rationale: [为什么绕过冲突检索——永久记录；不会自动过期]
  

  This field is visible in every /portfolio-status, every /matter briefing, and every /matter-update until it is removed. This skill does not remove it automatically — only when the user explicitly edits _log.yaml and only after the conflict is actually cleared.

3. Source

How did this matter come in?

• 律师函 | 起诉状送达 | 调查令/协查通知 | 行政监管问询 | 内部报告 | 诉前威胁

4. Risk triage — against firm calibration

• Severity: High | Medium | Low (refer to ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md 's severity grading)
• Likelihood: High | Medium | Low (refer to the likelihood grading)
• Overall risk rating (matrix result): High | Medium | Low | Critical
• Damages exposure range (best estimate)
• Non-monetary exposure (injunction? administrative penalty? reputational impact? precedent effect?)

5. Materiality

Against the firm thresholds in ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md :

• 需计提 | 已披露 | 监控中 | 不适用

6. Outside counsel

• Firm
• Lead partner
• Engagement letter status:已签署 | 待定 | 无
• Budget authorization: amount and approver

If risk is medium or above and no outside counsel is designated — flag it.

7. Internal owners

From ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/CLAUDE.md practice background — which internal stakeholders need to be involved?

• Business owner
• HR owner (if labor dispute)
• Communications contact (if reputational risk)
• Information security owner (if data or cybersecurity is involved)
• Other

8. Evidence preservation

• Has it been issued? If so: date, scope, custodians (list of names).
• Next refresh date (default: six months after issuance; adjust per matter).
• If not, and this matter is in litigation or reasonably expected to enter litigation: flag urgently.

9. Key dates

• Response deadline (answer, objection, counterclaim)
• Next hearing/pre-trial conference
• Statute of limitations deadline (if applicable)
• Any administrative regulatory deadline

10. Initial posture

One-paragraph theory:

• What is our case theory?
• What is the opposing party's case theory?
• What are the key facts?
• Initial posture:积极应对 | 寻求和解 | 调查中 | 观望

Write to output

Code name

Lowercase, hyphens, year at the end. Example:acme-v-us-2026、employment-smith-2026、ftc-inquiry-2026。

Before writing, confirm in _log.yaml that the code name is unique.

~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/matter.md

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

# [案件名称]

**代号：** [slug]
**立案/登记日期：** [YYYY-MM-DD]
**我方地位：** [原告/被告等]
**状态：** [status]

---

## 标识信息

[对方、管辖、案件类别、案由、来源]

## 利益冲突

**状态：** [已通过 / 待定 / 未运行 / 已豁免]
**方式：** [事务所/外聘律师/其他]
**审查人：** [姓名]
**审查日期：** [YYYY-MM-DD]
**审查对象：** [已运行的实体]
**备注：** [任何标注但已通过的事项、豁免引用（如适用）]

## 风险分流

**严重性：** [分级] —— [理由，引用事务所严重性定义]
**可能性：** [分级] —— [理由]
**风险评级：** [高/中/低/危急]
**敞口：** [金额范围 + 非金钱敞口]

## 重要性

[需计提/已披露/监控中/不适用——附计提金额、披露位置或不适用理由]

## 外聘律师

[律所、主办人、委托状态、预算]

## 内部负责人

[相关方及各自参与理由]

## 证据保全

[状态、日期、范围]

## 关键日期

[列表]

## 初始理论

[一段：我方案件逻辑、对方案件逻辑、关键事实、初始姿态] `[需审查——登记时的理论是工作假设；在任何以此假设为前提的诉讼行为或实质性沟通前应经外聘律师确认]`

## 待解决问题

[任何尚未知晓但重要的事项——如"保险通知待定"、"是否涵盖X事项尚不明确"]

~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/[slug]/history.md

Seed the history file with this registration as record zero:

# 历史记录：[案件名称]

仅追加的事件日志。最新记录在最前。

---

## [YYYY-MM-DD] —— 案件立案/登记

[来源、由谁引入、初始分流摘要、外聘律师指定情况、证据保全发出情况（是/否）。]

Append to ~/.claude/plugins/config/claude-for-legal-zh/litigation-legal/matters/_log.yaml

Add rows by pattern. Example:

- id: acme-v-us-2026
  name: "某某公司诉我方合同纠纷案"
  type: contract
  role: defendant
  counterparty: "某某公司"
  jurisdiction: "北京市朝阳区人民法院"
  status: active
  stage: pleadings
  source: complaint-served
  outside_counsel:
    firm: "某某律师事务所"
    lead: "张律师"
    email: "zhang@example.com"
    engagement: signed
  conflicts:
    status: cleared
    method: firm
    cleared_by: "内部法务"
    cleared_date: 2026-04-20
    override:
      by: null
      date: null
      rationale: null
  risk: high
  materiality: reserved
  exposure_range: "200万-500万元"
  internal_owners:
    business_lead: "业务负责人"
    hr_partner: null
    comms_contact: null
  legal_hold:
    issued: true
    issued_date: 2026-02-15
    scope: "销售部门 2023-2026"
    custodians: ["张三", "李四", "王五"]
    last_refresh: 2026-02-15
    next_refresh: 2026-08-15
    released: null
  related_matters: []
  opened: 2026-04-20
  next_deadline: 2026-05-15
  last_updated: 2026-04-20
  path: matters/acme-v-us-2026/

Confirm before writing

Show the user the log lines and the matter.md content:

This is what I am going to write. Please flag any errors or deficiencies before the actual write.

Close with the next-step decision tree

Close with the next-step decision tree in CLAUDE.md ## 输出 Close 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, gather more facts, observe and wait, other options) are a starting point, not locked-in items. The decision tree itself is the output; the lawyer chooses.

What this skill does not do

• Run a conflicts check on its own. Record the result, status, method, and reviewing entity. The actual review is done in whatever system (or judgment) the firm's practice profile states. If the user says "cleared," this skill takes it at face value and records the metadata.
• Decide the initial theory. Record what the user says; do not invent one on its own.
• Issue a litigation hold notice. Flag it if missing. The user issues it.