superdoc-redlines

Merge multi-agent AI edits into DOCX files as tracked changes using stable block IDs.

46|25|Updated May 7, 2026
One-click install
npx skills add https://github.com/LegalQuants/lq-skills --skill superdoc-redlines-legalquants
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superdoc-redlines
Source: https://github.com/LegalQuants/lq-skills/tree/main/skills/superdoc-redlines
Command: npx skills add https://github.com/LegalQuants/lq-skills --skill superdoc-redlines-legalquants

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Superdoc-redlines solves the problem of safely turning multiple sets of AI edits into native DOCX files with tracked changes, without relying on fragile text matching that breaks under formatting differences.

Core Features & Use Cases

  • Stable block ID mapping: Applies edits by referencing stable document blocks instead of searching by content, improving robustness across formatting changes.
  • Multi-agent edit merging: Combines edits from multiple reviewers and flags incompatible overlaps rather than silently overwriting work.
  • Native Word revision output: Produces a DOCX with Word revision marks so authorship and audit trail are preserved for review.

Quick Start

Use superdoc-redlines when you need to apply multi-agent AI edits to contract.docx and produce a DOCX with native Word tracked changes from the provided agent edit instructions.

Frequently Asked Questions about superdoc-redlines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge multiple AI edits into a DOCX file as tracked changes?

You can merge multi-agent AI edits into a DOCX file as native tracked changes by using stable block ID mapping. This process applies revisions deterministically by referencing document blocks instead of fragile text matching, preserving authorship and audit trails.

Why do my AI redlines break when formatting changes in a Word document?

AI redlines often break because they rely on fragile text matching that fails under formatting differences. Applying edits by referencing stable document block IDs instead of searching by content improves robustness across formatting changes and ensures valid revision XML insertion.

What is the best way to apply multi-agent redlining to contracts without Microsoft Word?

The best way to apply multi-agent redlining without Word is using headless processing that parses DOCX blocks and inserts native revision XML. This approach deterministically merges edits and surfaces conflicts for overlapping changes without requiring a Word environment.

Can I combine edits from multiple AI reviewers and flag overlapping changes in DOCX?

Yes, you can combine edits from multiple AI reviewers by merging multi-agent edits. The system flags incompatible overlaps rather than silently overwriting work, resolving conflicts and inserting revisions with agent attribution to maintain a clear audit trail.

Does deterministic redlining support agent attribution for native Word revision marks?

Deterministic redlining supports agent attribution by producing a DOCX with native Word revision marks. It maps insertions and revisions by block ID, ensuring that authorship from multiple agents is preserved for downstream review.

What are the limitations of using block ID mapping for DOCX conflict resolution?

Block ID mapping for DOCX conflict resolution requires parsing DOCX blocks and handling overlapping edits. Limitations arise if the input lacks stable block structures, making conflict surfacing and valid revision XML insertion difficult without proper agent edit instructions.