Contract Modification (AI Revision Mode) Plus

The hardest part of contract review is often not finding issues, but turning findings into an editable redline: which clauses can be fixed directly, which business choices require user decisions, and which legal citations need verification. This skill works directly on the uploaded contract text, applying w:del / w:ins tracked changes for definite fixes and Word comments for items that need user judgment, rather than producing a separate clean draft.

Core Capabilities And Workflow

• Stance preselection: After upload, it asks for the modification perspective: pro-Party A, pro-Party B, neutral, or custom needs; when a party stance is selected, it loads the corresponding Playbook as the review baseline.
• Redline/comment routing: Findings are mapped to delete, insert, replace, or comment; directable fixes are applied as tracked changes, while business trade-offs, factual gaps, and authorization-dependent issues are added as comments.
• Legal citation verification: When legal provisions, judicial interpretations, or case numbers are involved, it attempts verification via yuandian-mcp; unverified items are marked for manual review instead of being inserted into tracked changes.
• Counterparty risk precheck: If qcc-company or yuandian-mcp is connected, it asks whether to query litigation, enforcement, or dishonest-debtor records; the conclusion is flagged as potentially outdated and for reference only.
• Deliverable: It outputs {contract_name}_revised_{YYYYMMDD}.docx with tracked changes and comments, including page numbers.

Boundaries And Notes

The skill is useful for lawyers, legal teams, or contract operations staff drafting a first-pass contract revision, but it does not provide legal advice. All revisions should still be reviewed by qualified legal professionals. Inputs can be DOCX, PDF, or pasted text; PDF or plain text must be converted to DOCX before native tracked changes and comments can be applied.