If the user provides partial context, proceed with what you have and note assumptions.

Step 3: Load the Playbook

Look for the organization's contract review playbook in local settings (e.g., legal.local.md or similar configuration files).

The playbook should define:

• Standard positions: The organization's preferred terms for each major clause type
• Acceptable ranges: Terms that can be agreed to without escalation
• Escalation triggers: Terms that require senior counsel review or outside counsel involvement

If no playbook is configured:

• Inform the user that no playbook was found
• Offer two options:
  1. Help the user set up their playbook (walk through defining positions for key clauses)
  2. Proceed with a generic review using widely-accepted commercial standards as the baseline
• If proceeding generically, clearly note that the review is based on general commercial standards, not the organization's specific positions

Step 4: Clause-by-Clause Analysis

Apply the following review process:

1. Identify the contract type: SaaS agreement, professional services, license, partnership, procurement, etc. The contract type affects which clauses are most material.
2. Determine the user's side: Vendor, customer, licensor, licensee, partner. This fundamentally changes the analysis (e.g., limitation of liability protections favor different parties).
3. Read the entire contract before flagging issues. Clauses interact with each other (e.g., an uncapped indemnity may be partially mitigated by a broad limitation of liability).
4. Analyze each material clause against the playbook position.
5. Consider the contract holistically: Are the overall risk allocation and commercial terms balanced?

Analyze the contract systematically, covering at minimum:

…

customer-research

围绕客户问题进行多来源调研与溯源，快速整理背景并支持准确回复。

vendor-review

帮助你评估供应商方案，完成成本、风险与采购建议分析