rumo-document-writing git:20261016.b3c4708A

Immutable. This exact content never changes and is served at /api/v1/blob/d3c123bec5350b1a.

---
name: rumo-document-writing
description: Use when drafting, revising, splitting, formatting, or quality-checking formal Word delivery documents such as designs, reviews, tests, acceptance materials, deployment manuals, operations manuals, interface documents, and technical reports.
---

# Document Writing

Use the document toolchain for DOCX mechanics and rendering. This skill governs evidence, product-boundary wording, formal structure, and delivery quality.

Follow the requested audience, language, organization template, terminology, and source document. When those rules are project-specific, resolve them through `rumo-project-profile`.

- Preserve existing images, tables, page breaks, headers, footers, numbering, styles, and tracked requirements unless the user asks to redesign them.
- Translate source and code evidence into stable product concepts without leaking local paths, generation notes, Markdown markers, temporary filenames, or implementation details outside scope.
- Distinguish design, implementation, test, deployment, and field-acceptance evidence.
- Do not claim verification or acceptance that was not actually obtained.
- Render the final DOCX to page images and inspect every page for overflow, clipping, broken tables, orphan headings, inconsistent spacing, and unreadable diagrams.

Deliver the final document and summarize material changes, evidence used, and remaining acceptance boundaries.