docx-official

DOCX Skill

An Apache-2.0 toolkit for producing, editing, and reading Microsoft Word (.docx) files, written against the public ECMA-376 / ISO/IEC 29500 specification. Runtime libraries: python-docx (MIT) and lxml (BSD-3-Clause). LibreOffice (soffice) is an optional external binary.

Pipeline

Run these phases in order. Two are gates: do not pass a gate on your own judgement.

Phase 0  Read the source and the workspace
Phase 1  Settle the brief            <- ask once, bounded
Phase 2  Heading tree + style        <- GATE: user approves before drafting
Phase 3  Draft
Phase 4  Verify and repair           <- loop until it passes
Phase 5  Hand off

Phase 0 — Read. Read the source, and look for a template, an earlier document of the same kind, or a style guide in the workspace. That reading is what tells you which questions are still open.

Phase 1 — Settle the brief. Reader, purpose, length, and register decide what the document is. Take from context whatever context answers, then ask about the rest in one ask_user call — at most three questions, options with a marked recommendation. Skip this phase for an edit, a template fill, or an explicit brief. Read interview.md for what to ask, what to answer yourself, and what the Phase 2 plan must contain.

Phase 2 — Heading tree and style, then stop. Write the heading tree, one line per section stating what it must establish, the style basis, your assumptions, and every fact the material does not support. Put it in front of the user and wait. Rewriting an outline costs a sentence.

Phase 3 — Draft. Write inside the approved tree using named styles, not direct formatting. Do not add sections the plan does not contain.

Phase 4 — Verify and repair. Run the QA checklist and document_preview, fix what they report, run them again.

Phase 5 — Hand off. File path, style basis, the checks that actually ran, and every placeholder still open.