About this skill

Problem

Corporate .docx templates often carry fixed covers, headers, footers, custom heading styles, and placeholder text. Directly asking a model to “write from the template” can break styles, generate unsupported TOC entries, drop code blocks, clip images because of line_spacing_rule = EXACTLY, or exceed token limits in long documents.

How It Works

The skill runs a six-stage pipeline: Template Analysis, Spec, Plan, Research, Authoring, and Injection, in order. It uses python-docx copy-and-inject instead of whole-file pandoc conversion, and renders Mermaid diagrams before embedding them in .docx output. Key practices include validating output directories and source whitelists, identifying custom heading styles and confirming the TOC mapping, requiring every TOC entry to have source evidence from code paths, document sections, or feature lists, writing chapters as independent Markdown files to limit context length, and auditing Normal spacing, Heading numPr, non-Mermaid code blocks, and placeholder text before injection.

Boundaries

Use it for fixed-template enterprise design documents, technical specifications, white papers, interface/database docs, and mixed .docx + .xlsx + .pptx tasks. Avoid it for plain Markdown, READMEs, or simple local .docx edits. Confirm template path, source scope, deliverables, and TOC mapping before starting.

Screenshots

Use Cases

Deliver a design outline from a corporate .docx template while preserving cover, headers, footers, and TOC.
Turn xlsx feature lists, interface notes, and code references into detailed design and interface documentation.
Rewrite selected chapters from an old .docx draft and re-inject into the template without style or TOC drift.
Render Mermaid architecture diagrams into .docx and keep JSON, SQL, or pseudocode blocks visible.

Best For

Software engineers producing outline or detailed design docs need source code and references injected into company templates.
Technical writers assembling interface, database, or white-paper docs from fixed corporate templates.
Architects delivering pre-review .docx proposals with TOC, diagrams, and code blocks.
Product-tech leads mapping xlsx feature lists and pptx architecture diagrams into formal document chapters.