Official Document Workflow

Problem to Solve

Official document writing is not only about turning notes into paragraphs. It also requires selecting the correct document type, tracking missing required elements, restructuring fragmented material, keeping a formal tone, checking GB/T 9704-2012 formatting rules, and producing a reviewable DOCX. Without a controlled workflow, headings, indents, fonts, spacing, issuer fields, and audit notes can cause repeated rework.

How It Works

The skill uses an Orchestrator to coordinate logical roles: Intake Expert identifies task mode, document type, and missing fields; Drafting Expert builds the first draft from available facts; Restructure Expert analyzes source material; Style Expert improves official wording without changing facts; Format Audit Expert checks rules in references/authority-gbt9704.md; and DOCX Tool Expert generates, formats, or inspects Word files with scripts/format_docx.py and scripts/check_format.py.

It supports three workflows:
- Mode A: New document: identify document type and required elements, ask only when blocked, then produce draft.md, format-audit.md, and final.docx when requested.
- Mode B: Revision: preserve facts, figures, dates, names, and policy references; create structure-analysis.md before producing revised-draft.md.
- Mode C: Format audit: audit DOCX, Markdown, or plain text and report pass/fail findings with required fixes.

Boundaries and Notes

The skill is aimed at compliant document bodies and review drafts, not full red-header issuance. It does not create the formal masthead, red separator line, or signer block. DOCX scripts require Python 3 and python-docx; heading detection depends on Chinese ordinals or Markdown levels, and heading lines should be separate items. Style edits must not alter facts, and conflicts between user requests and formal standards should pause for confirmation.