office-document-workflow

name

office-document-workflow

description

Workflow guidance for Codex agents creating, editing, reviewing, redlining, commenting, formatting, converting, or QA-checking Microsoft Word, WPS Office, DOCX, Office document, and Google Docs-targeted files through available Office document tools or MCP/plugin integrations. Use for WPS/Word reports, proposals, contracts, briefs, templates, tracked changes, comments, document cleanup, metadata/privacy checks, and Chinese requests about WPS, Word, docx, wendang, gongwen, hetong, or baogao.

Office Document Workflow

Purpose

Use this skill to guide WPS/Word/DOCX document work through whatever Office-capable tooling is available in the current Codex environment. It does not implement an MCP server. It provides a safe, reproducible workflow for using installed document tools, plugins, Word MCP servers, or local Office-compatible libraries.

First Check

Before editing or creating a document:

• Identify the requested output: .docx, PDF, Google Docs, Markdown, template, redline, comments, or extracted content.
• Check whether the environment exposes a document plugin, Office MCP server, bundled workspace dependencies, or file conversion tools.
• If using a Word MCP server over stdio, prefer a clean stdio wrapper that suppresses startup banners and stdout noise before MCP JSON-RPC begins.
• Preserve the original file unless the user explicitly asks to overwrite it.
• Use absolute paths for source and output files.

Workflow

1. Understand the document task.

   • Create, edit, summarize, format, compare, redline, comment, merge, anonymize, or export.
   • Identify audience, tone, page size, language, and required template.

2. Plan the document structure.

   • Use real headings, lists, tables, captions, headers, and footers.
   • Avoid fake bullets, fake headings, and manual spacing that will break in Word.

3. Build or edit the DOCX.

   • Prefer official Office/MCP/plugin capabilities when available.
   • Use structured document APIs or OOXML-aware libraries when needed.
   • Keep tables explicit: fixed columns, readable wrapping, repeating headers when useful.

4. Review and verify.

   • Render or export to a visual format when possible.
   • Inspect pages for clipped text, broken tables, missing fonts, bad page breaks, and header/footer problems.
   • Check that comments, tracked changes, fields, footnotes, and references are structurally valid.

5. Deliver.

   • Provide only the final requested deliverable unless the user asks for intermediate QA files.
   • Mention any verification that could not be completed.

Common Tasks

• Create a polished report or proposal from notes.
• Apply tracked changes to a contract or manuscript.
• Add comments to specific paragraphs.
• Convert Markdown or outline content into a formatted DOCX.
• Clean metadata before sharing.
• Merge multiple DOCX files into a consistent final document.
• Use WPS Office as a practical compatibility target when local testing shows it renders the generated DOCX best.

Quality Checklist

• The document opens cleanly in Word or an Office-compatible viewer.
• Styling uses real Word concepts, not manual visual hacks.
• Tables and images do not overflow page margins.
• All requested comments, redlines, or edits are present.
• Sensitive metadata is removed when requested.
• The final file path is clear and absolute.