edit-contract

Edit contract

Edit an existing legal document using the smallest redline that achieves the user's instruction.

Non-negotiable tracked changes rule

Before editing the document, ensure tracked changes are enabled and used for every modification. Keep them enabled throughout the work. Do not accept or reject tracked changes unless the user explicitly asks you to do so.

When NOT to Use

• Reviewing a contract against a supplied playbook — use review-contract.
• Explaining what changed between marked-up versions — use summarize-redlines.
• Drafting a new agreement from a template or precedent — use draft-new-contract.
• Finding broken cross-references or defined term problems without editing — use check-cross-references or check-defined-terms.
• Legal advice, or deciding which position the user should take.

Hand-off rule. If a request, or part of one, matches an item above that names another skill, do not do that part here — even when the documents are already open and the work looks quick. Name the skill that handles it (for example, "That part is a job for review-contract") and stop that part; finish only what belongs to this skill. If the named skill is not installed, say so plainly and do not attempt it here.

Workflow

1. Confirm the document and the requested outcome.
2. Read every relevant provision, definition, cross-reference, table, heading, and surrounding passage before making changes. When opening a document, use a method that shows tracked changes and comments, and check whether any are present before relying on the text.
3. Form one high-level plan for the complete requested change. Identify each target, operation, intended legal effect, placement dependency, and ordering dependency.
4. Plan all requested changes to the same paragraph, clause, table, or other target together, but execute each change at the smallest text range or structural unit that can represent it without redlining unchanged content.
5. Make the complete minimal set of edits in logical document order. Prefer exact insertions, deletions, and substitutions over replacement of a containing paragraph or clause. Apply independent edits together when the editing system supports it; apply dependent edits sequentially.
6. Verify each edit after it is made. Preserve successful edits and correct only failed edits rather than recreating work that has already been verified.
7. Review the resulting document in context, including affected definitions and cross-references, and confirm that it implements the complete request without unintended changes.
8. Summarize what changed and clearly identify anything that could not be completed.