Official Document Formatter

The Problem

Formatting official documents and reports often stalls on small details: red headers, fonts, line spacing, page numbers, attachments on a separate page, and signature indentation. This skill works on already-written document content and turns GB/T 9704-2012 requirements into an executable checklist, then produces a reviewable docx file. It does not rely on cloud rendering; its focus is on enforcing formatting rules through locally verifiable document properties.

How It Works

It follows a three-step workflow:
- Extract requirements: parse the formatting guide for page setup, fonts, header, body, page numbers, and common pitfalls, then generate an execution checklist.
- Build step by step: use python-docx to write the red header, title, body hierarchy, line spacing, page-number fields, and attachment rules; if a font or pandoc is missing, it degrades to txt / md and says so explicitly.
- Verify strictly: a validation script checks Word-rendering-relevant properties, such as first-line indent, red separator line, w:fldSimple PAGE fields, and attachment page breaks, and returns to the build step on failure.

Boundaries

It is intended for formatting normalization and demo generation, not for drafting official content. Built-in samples only demonstrate the red-header, title, and signature structure. Formal external documents still need to be checked against the issuing unit's own rules. For document QA or journal-level re-layout, route to the corresponding skill.