The LegalWork Atlas LegalWork's documentation, bound to the code it describes
17 documents

The legal-document engine

LegalWork's actual legal work is defined as firm-owned agent prompts, not app code. This path walks the two flagship workflows — Word redlining and tabular review — from the user command down to the read-only subagents that do the work.


description: Agentic Word editing — redline and comment on a .docx as reviewable tracked changes

Edit a Word document with AI — write back comments and tracked-change redlines the lawyer reviews and accepts in the in-app viewer (the firm's open-model version of "ask the assistant to redline this contract").

Load and follow the docx-edit skill, then carry out this request:

$ARGUMENTS

Reminders from the skill:

  • inspect the .docx first to get the stable paragraph map; anchor every edit to a 0-based paragraphIndex.
  • For a full redline pass, fan out the docx-redliner subagent (Task tool); for a small targeted change, build the plan yourself.
  • comments are margin notes (the why); proposals are tracked-change edits. Every search string must be verbatim from the paragraph.
  • apply writes a non-destructive <base>.redlined.docx by default — open it in the viewer to see the redlines inline. Use --in-place only if asked.
  • Report any ops that didn't match verbatim instead of dropping them; never fabricate parties, numbers, or terms.

If no document is named in the arguments, ask which .docx to edit first.