Word Document Workflows
Tech Stack Target / Version: Word desktop or python-docx automation with current OOXML-compatible workflows.
Use this skill when .docx layout and document structure matter, not just the raw text.
- Leverage native parallel subagent dispatch and 200k+ context windows where available.
Current MCP Reality
Microsoft publicly documents a Word MCP server in the Microsoft 365 Agents Toolkit preview, but tool availability still depends on the host. In GitHub Copilot you may see Word-specific tools; in other clients they may be missing. If direct Word MCP access is unavailable, use the included local script workflow.
Activation Conditions
Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
- Creating or editing
.docx reports, memos, or structured deliverables
- Applying headings, tables, images, or styles
- Reviewing or extracting document structure
- Preparing Word output before a later PDF conversion
Practical Workflow
- Confirm whether the client exposes Word MCP capabilities.
- Start with structure: title, headings, sections, tables.
- Apply styling consistently only after the structure is right.
- Validate comments, footnotes, and references before export.
- Use the local generator script when MCP access is unavailable.
MCP Fallback – Native Automation
When MCP is unavailable, use native automation: python-docx for .docx, direct OOXML inspection for unsupported structures, and PDF export checks when layout matters. Preserve styles, tables, headers, footers, comments, tracked-change expectations, and metadata, then reopen or parse the document before claiming success.
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/word-document and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Word Document MCP
- Fallback prompt: "Use the Word Document Workflows skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
- Use
python-docx, Word desktop, or document export scripts when the MCP surface is unavailable.
- Re-open or render the document locally so formatting, comments, and pagination are verified before delivery.
- Do not claim an MCP operation was used when the active host does not expose it.
Anti-Patterns
- Writing for the author instead of the reader: It bakes in unstated context and leaves the actual audience unsure what to do next.
- Skipping concrete examples or commands: Abstract guidance is easy to approve and hard to apply correctly.
- Letting links, screenshots, or versions drift: Polished formatting does not help if the instructions are no longer true.
Verification Protocol
Before claiming "skill applied successfully":
- Pass/fail: The Word Document artifact type, target format, and required output fidelity are stated before editing.
- Pass/fail: MCP availability is checked and the native automation fallback path is named when MCP is absent.
- Pass/fail: The produced file or formula is opened, parsed, rendered, or otherwise validated locally.
- Pressure-test scenario: Apply the workflow to a file with formatting, metadata, or conversion edge cases and verify nothing important is lost.
- Success metric: Zero unverified document claims; the artifact itself is the evidence.
Document Checklist
References & Resources
Documentation
Scripts
Examples
Related Skills
1---
2name: word-document
3version: "2.0"
4last_updated: 2026-09-08
5tags: [docs, document, writing, quality, templates]
6description: "Word (.docx) manipulation via MCP server. Use for reading, creating, editing, formatting Word documents including tables, footnotes, comments, images, headers, styles, and PDF conversion."
7metadata:
8 source: https://skillmd.com/skills/practicalswan/word-document
9---
10
11# Word Document Workflows
12
13> Tech Stack Target / Version: Word desktop or `python-docx` automation with current OOXML-compatible workflows.
14
15Use this skill when `.docx` layout and document structure matter, not just the raw text.
16
17- Leverage native parallel subagent dispatch and 200k+ context windows where available.
18
19
20## Current MCP Reality
21
22Microsoft publicly documents a Word MCP server in the Microsoft 365 Agents Toolkit preview, but tool availability still depends on the host. In GitHub Copilot you may see Word-specific tools; in other clients they may be missing. If direct Word MCP access is unavailable, use the included local script workflow.
23
24## Activation Conditions
25
26Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
27
28- Creating or editing `.docx` reports, memos, or structured deliverables
29- Applying headings, tables, images, or styles
30- Reviewing or extracting document structure
31- Preparing Word output before a later PDF conversion
32
33## Practical Workflow
34
351. Confirm whether the client exposes Word MCP capabilities.
362. Start with structure: title, headings, sections, tables.
373. Apply styling consistently only after the structure is right.
384. Validate comments, footnotes, and references before export.
395. Use the local generator script when MCP access is unavailable.
40
41## MCP Fallback – Native Automation
42
43When MCP is unavailable, use native automation: `python-docx` for `.docx`, direct OOXML inspection for unsupported structures, and PDF export checks when layout matters. Preserve styles, tables, headers, footers, comments, tracked-change expectations, and metadata, then reopen or parse the document before claiming success.
44
45<!-- MCP:START -->
46
47<!-- PORTABILITY:START -->
48## Cross-Client Portability
49
50This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
51
52- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
53 workflow in project instructions when folder discovery is unavailable.
54- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
55- Codex: install or sync the folder into
56 `$CODEX_HOME/skills/word-document` and restart Codex after major changes.
57
58<!-- PORTABILITY:END -->
59
60## MCP Availability And Fallback
61
62Preferred MCP Server: Word Document MCP
63
64- Fallback prompt: "Use the Word Document Workflows skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
65- Use `python-docx`, Word desktop, or document export scripts when the MCP surface is unavailable.
66- Re-open or render the document locally so formatting, comments, and pagination are verified before delivery.
67- Do not claim an MCP operation was used when the active host does not expose it.
68
69<!-- MCP:END -->
70
71## Anti-Patterns
72
73- Writing for the author instead of the reader: It bakes in unstated context and leaves the actual audience unsure what to do next.
74- Skipping concrete examples or commands: Abstract guidance is easy to approve and hard to apply correctly.
75- Letting links, screenshots, or versions drift: Polished formatting does not help if the instructions are no longer true.
76
77## Verification Protocol
78
79Before claiming "skill applied successfully":
80
811. Pass/fail: The Word Document artifact type, target format, and required output fidelity are stated before editing.
822. Pass/fail: MCP availability is checked and the native automation fallback path is named when MCP is absent.
833. Pass/fail: The produced file or formula is opened, parsed, rendered, or otherwise validated locally.
844. Pressure-test scenario: Apply the workflow to a file with formatting, metadata, or conversion edge cases and verify nothing important is lost.
855. Success metric: Zero unverified document claims; the artifact itself is the evidence.
86
87## Document Checklist
88
89- [ ] Heading hierarchy is clear
90- [ ] Tables are readable and consistently styled
91- [ ] Comments or review notes are intentional
92- [ ] Placeholder text is removed
93- [ ] The final document was re-opened or otherwise verified after generation
94
95## References & Resources
96
97### Documentation
98- [DOCX Formatting Reference](./references/docx-formatting-reference.md) - Practical formatting notes and document structure guidance
99
100### Scripts
101- [DOC Template Generator](./scripts/doc-template-generator.py) - Local fallback for generating Word-ready document structures
102
103### Examples
104- [Report Generation Example](./examples/report-generation-example.md) - Example report workflow for `.docx` output
105
106## Related Skills
107
108- [documentation-authoring](../documentation-authoring/SKILL.md): Use it when the workflow also needs drafting structured technical or product documents.
109- [documentation-patterns](../documentation-patterns/SKILL.md): Use it when the workflow also needs reusable documentation structures and templates.
110- [documentation-quality](../documentation-quality/SKILL.md): Use it when the workflow also needs documentation review standards and quality gates.
111- [documentation-verification](../documentation-verification/SKILL.md): Use it when the workflow also needs final documentation validation before publishing.