amendment-history

To trace contract amendments across multiple versions, this Skill reads a base agreement and subsequent revisions in chronological order, parsing modified, added, or deleted provisions to build a time-ordered change record. It produces a cross-contract summary or a provision-specific trace quoting exact text.

Yes, you can trace a specific clause by using provision trace mode. This mode quotes prior and current language for a named clause across uploaded contract revisions, providing exact text with inline section references so you can verify which language controls now.

Finding which contract language controls after several addenda requires chronological amendment tracking. The Skill sequences a base agreement and addenda to show what changed, flags inconsistencies like conflicting edits or shifted section numbering, and identifies the latest controlling language with section-anchored references.

To get a summary of changes across contract revisions, use summary mode. This mode reads a base agreement and subsequent amendments in sequence to produce a full cross-contract overview of modifications over time, highlighting inconsistencies with inline section references for reviewer verification.

Yes, amendment history analysis includes watch-item flagging that highlights inconsistencies such as conflicting edits, shifted section numbering, and party-name changes. Every flagged item includes inline section references so reviewers can quickly locate and verify issues in source documents.

To reconstruct an amendment history for a legal workflow, upload a base agreement and its subsequent amendment or addenda files. Once uploaded, request either a full amendment summary or a clause-specific trace to generate a time-ordered change record with section-anchored outputs.