Word Revision Workflow

---
name: word-revision-workflow
description: "Use when an agent must perform editorial revision of .docx files with reviewer comments, Track Changes, claim checks against a source, restricted edits, and selective accept. Triggers on \"word revision\", \"docx review\", \"track changes\", \"claim check\", \"brand guidelines\". Non-triggers: Google Docs Sheets or Slides editing (use google-workspace-ops), format conversion without editorial review (use nutrient-document-processing). Outcome: reviewed .docx with triaged comments, verified claims, restricted Track Changes edits, and selective accept log."
metadata:
  origin: ECC
---

# Word Revision Workflow

Editorial revision of .docx files with an agent, end to end: triage reviewer
comments -> edit with Track Changes -> check each claim against its source ->
apply restricted edits -> run a brand-guidelines pass -> accept selectively.

This skill covers the Office gap: `google-workspace-ops` is Google-only and
`nutrient-document-processing` is conversion, not editorial review.

## When To Activate

- The user says Word revision, docx review, Track Changes, reviewer comments,
  accept or reject changes, or brand-guidelines pass on a document.
- A .docx file has open comments or pending tracked changes that need triage
  before any edit.
- Factual claims in the document must be verified against a stated source
  (for example a shared drive folder or content repository) before acceptance.
- The revision must keep an audit trail of what was accepted, rejected, or
  left pending.

## Workflow

### 1. Collect inputs and freeze scope

- Gather the .docx file, the list of reviewers, the source of truth for
  claims, and the brand or style guide to enforce.
- Record document name, revision date, and reviewer list in a short header
  at the top of the working log (`output/revision-log.md`).
- Do not start editing until inputs are complete. Missing source = stop.

### 2. Triage comments

- Extract every comment with author, page or paragraph anchor, and status.
- Classify each comment as [x] actionable, [ ] question for the author,
  or [ ] out of scope.
- Order actionable comments by document order, not by reviewer.
- Questions for the author go to a pending list; never guess the answer.

### 3. Enable Track Changes and draft edits

- Turn Track Changes on before any edit so every insertion and deletion
  is visible to the reviewer.
- Make one edit per comment where possible so accept can stay selective.
- Keep formatting edits separate from content edits.

### 4. Check each claim against the source

- For every factual claim touched by an edit, locate the matching passage
  in the declared source and quote it in the working log.
- Mark each claim as OK (source supports it), MISMATCH (source
  contradicts it), or UNVERIFIED (no source found).
- MISMATCH and UNVERIFIED block acceptance of that edit until resolved.

## Exemplo

```text
.docx com 12 comentários: tria ([x] acionável / [ ] pergunta / fora) por ordem do doc
Track Changes ligado; 1 edit por comentário; claim "cresceu 40%" → fonte citada OK
MISMATCH trava o aceite; log registra aceito/rejeitado/pendente por item
```

### 5. Apply restricted edits

- Allowed: grammar, spelling, punctuation, consistent terminology,
  formatting required by the style guide, and claim corrections backed
  by a quoted source.