escalation-flagger

/escalation-flagger

Based on the escalation matrix in the review guidelines, identify the approver for the contract issue and draft the message.

Instructions

Load the review guidelines → escalation section. If missing, state that — the business area configuration needs editing.
Characterize the issue: amount threshold / clause deviation / automatic trigger / business decision.
Match the matrix, identify the approver. Be specific — a person or role, not "legal leadership".
Draft the escalation note per the template: contract content, review guidelines position, options with recommendations, decision deadline.
Do not send. Draft, present, let the lawyer send.

Examples

/commercial-legal:escalation-flagger
Acme主协议有无上限的责任——谁批准，我说什么？

/commercial-legal:escalation-flagger
参考：acme-review-memo.md
问题：§8.2 赔偿例外排除

Matter context

Matter context. Check the business area-level CLAUDE.md for ## 事项工作区. If Enabled is ✗, skip this section. If enabled and there is no active matter, ask.

Purpose

Every contract team has an escalation matrix, whether or not it is written down. This skill reads the written matrix, matches contract issues to it, identifies the approver, and drafts the escalation note.

Load the matrix

Which side? Before matching the matrix, determine which side the company is on in this contract. Read the matching review guidelines section to assess whether the clause is within the concession range or triggers automatic escalation.

Read review guidelines → ## 上报. If missing or ambiguous, state that — the cold-start interview should have captured this.

Expected structure:

Can approve	Threshold	Escalate to	Method
Legal assistant	Standard clauses, <500k yuan	Lead lawyer	Feishu
Lead lawyer	Non-standard but within concession range, <5m yuan	Legal lead	Feishu or email
Legal lead	Everything else	CFO/board	Meeting

Plusautomatic escalation triggers— matters that require escalation regardless of amount. Typically: unlimited liability, IP assignment, anything on the "never accept" list.

Workflow

Step 1: Characterize the issue

What is being escalated? Amount threshold, clause deviation, automatic trigger, or business decision. If the clause is within the concession range, no escalation is needed.

Step 2: Match the matrix

问题是自动触发条件吗？
  → 是：上报至 [该触发条件指定的人]
  → 否：继续

合同价值是否超过审查者的阈值？
  → 是：上报至在该金额级别有审批权的人
  → 否：继续

条款偏离是否超出所有已记录的让步范围？
  → 是：上报至可以批准非标准条款的人
  → 否：审查者可以批准——不需要上报

Step 3: Identify the approver

Be specific. Not "escalate to legal leadership" — name the person or role in the review guidelines.

Step 4: Draft the escalation note

The approver should be able to decide from the message itself — no need for "let me pull up the contract and take a look".

**上报至：** [姓名]
**方式：** [飞书频道 / 邮件 / 会议 — 按审查指引]
**紧急程度：** [截止日期（如有）]

---

[姓名]你好——

需要你关于 [对方当事人] [协议类型] 的决定。[一句交易背景。]

**问题：** [一段中文。他们想要什么，为何超出我方标准，实际风险是什么。]

**合同原文：**
> "[精确引用]"

**审查指引说：** [引用审查指引]

**选项：**
1. **接受** — [一行说明为何这可能可以]
2. **驳回并附：** "[建议的对应语言]" — [一行说明对方可能的反应]
3. **终止** — [一行说明在商业背景下是否现实]

**我的建议：** [哪个选项及简要理由]

**需要决策日期：** [日期（如存在截止日期）]

[完整审查备忘录链接]

Step 5: Record the escalation

If the team uses a ticketing system or contract management system approval workflow, log it. If not, note in the review memo that the escalation was sent, to whom, and when.

Calibration: when in doubt, escalate with a note

The cost of an unnecessary escalation is roughly 30 seconds of the approver's time—reading it, saying "OK, go ahead." The cost of a missed escalation is signing unapproved terms, which is a one-way door. The costs are asymmetric.When in doubt, escalate.

What this skill does not do

Does not approve anything. Only routes.
Does not decide between options. The draft contains recommendations, but the approver decides.
Does not send escalation messages—only drafts them. The lawyer reviews and then sends.