Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Convert architecture documents (blueprints, stakeholder presentations) from Markdown to professionally formatted Word (.docx) files. Applies corporate styling, embeds PNG diagrams, and creates presentation-ready documents.
Markdown to Word Exporter
Convert architecture documents to professionally formatted Word documents (.docx) ready for stakeholder presentations, board meetings, and executive approvals.
๐ Converting markdown to Word document...
โ Detected document type: Stakeholder Presentation
โ Parsed markdown structure (11 sections, 47 pages)
โ Embedded 6 PNG diagrams from diagrams/ folder
โ Applied corporate styling (Calibri, professional theme)
โ Generated table of contents (3 levels, 28 entries)
โ Formatted 8 tables with headers and alternating rows
โ Added cover page with metadata
โ Added approval section with signature fields
๐ stakeholder-presentation.docx created (2.4 MB, 47 pages)
Ready for stakeholder review!
Next steps:
- Review document in Microsoft Word or Google Docs
- Customize cover page with company logo
- Adjust approval checklist if needed
- Export to PDF for distribution: File โ Export โ PDF
Customization Options
Optional parameters (ask user if they want to customize):
Company logo: Upload logo for cover page (PNG/SVG, max 200px height)
Color scheme: Default (blue), Corporate (gray), Custom (specify hex codes)
Page size: Letter (default), A4, Legal
Font: Calibri (default), Arial, Times New Roman
Confidentiality level: Confidential (default), Internal Use Only, Public
Version number: 1.0 (default), custom
Default behavior: Blue color scheme, Letter size, Calibri font, "Confidential" footer, version 1.0.
Export Options
Option 1: DOCX only
Use this skill to convert `stakeholder-presentation.md` to `stakeholder-presentation.docx`.
Option 2: DOCX + PDF
Use this skill with PDF export enabled.
# โ stakeholder-presentation.docx# โ stakeholder-presentation.pdf
Option 3: Custom styling
Use this skill with custom branding options such as logo, color theme, and A4 sizing.
# โ stakeholder-presentation.docx (A4, corporate colors, with logo)
Technical Implementation
Pandoc Conversion Command
#!/bin/bash# Convert markdown to DOCX with full styling
INPUT="stakeholder-presentation.md"
OUTPUT="stakeholder-presentation.docx"
TEMPLATE="template.docx"# Reference template with corporate styling# Create reference template if it doesn't existif [ ! -f "$TEMPLATE" ]; then
pandoc --print-default-data-file reference.docx > "$TEMPLATE"# Customize template.docx with corporate stylingfi# Convert with Pandoc
pandoc "$INPUT" \
-o "$OUTPUT" \
--reference-doc="$TEMPLATE" \
--toc \
--toc-depth=3 \
--number-sections \
--highlight-style=tango \
--resource-path=".:diagrams" \
--metadata title="Architecture & Implementation Plan" \
--metadata author="Architect AI" \
--metadata date="$(date +%Y-%m-%d)"echo"โ Created $OUTPUT"
Reference Template Creation
# Generate default template
pandoc --print-default-data-file reference.docx > template.docx
# Customize template.docx:# 1. Open in Microsoft Word# 2. Modify styles (Heading 1, Heading 2, Normal, etc.)# 3. Set page layout (margins, headers, footers)# 4. Configure table styles# 5. Save and close# Template is now ready for repeated use
PDF Export (if requested)
# Option A: Use LibreOffice (headless)
libreoffice --headless \
--convert-to pdf \
stakeholder-presentation.docx \
--outdir .
# Option B: Use Pandoc with LaTeX
pandoc stakeholder-presentation.md \
-o stakeholder-presentation.pdf \
--pdf-engine=xelatex \
--toc \
--number-sections
Error Handling
If Pandoc not installed:
Action: Fallback to markdown-to-docx library
Notify user: "โน๏ธ Using basic conversion (Pandoc not found). Install Pandoc for better formatting."
Notify user: "โ ๏ธ diagrams/ folder not found. Run /architect:export-diagrams first for embedded images."
If reference template missing:
Action: Generate default template on-the-fly
Notify user: "โน๏ธ Using default styling. Customize template.docx for corporate branding."
If input markdown not found:
Action: Error with guidance
Example: "โ stakeholder-presentation.md not found. Generate the stakeholder presentation markdown first."
Integration with Other Skills
Recommended workflow:
# 1. Generate blueprint
/architect:blueprint
# 2. Create stakeholder presentation markdown# 3. Export diagrams to PNG
/architect:export-diagrams
# 4. Use this skill to convert the markdown to DOCX# Result: stakeholder-presentation.docx ready for executives
Success Criteria
A successful DOCX export should:
โ Preserve all markdown content (no data loss)
โ Apply professional corporate styling
โ Embed all PNG diagrams at appropriate sizes
โ Generate table of contents with page numbers
โ Format tables with headers and alternating rows
โ Add cover page with metadata
โ Add headers/footers with page numbers
โ Include approval section with signature fields
โ Be editable in Microsoft Word or Google Docs
โ Be print-ready (proper margins, page breaks)
Files Created
stakeholder-presentation.docx # Main output (2-5 MB)
stakeholder-presentation.pdf # Optional PDF export
template.docx # Reference template (reusable)
File sizes:
DOCX: 2-5 MB (with embedded diagrams)
PDF: 1-3 MB (compressed diagrams)
Template: 50-100 KB
Advanced Features
Custom Branding
Replace default template with corporate template:
# 1. Create corporate template# - Open template.docx in Word# - Apply corporate fonts, colors, logo# - Save as corporate-template.docx# 2. Use this skill with the custom template during conversion
Batch Export
Export multiple documents at once:
# Export all markdown files in the current directory with this skill's batch workflow# Output:# โ blueprint.docx# โ stakeholder-presentation.docx# โ sprint-backlog.docx
Version Control
Automatically version documents:
Use this skill with document version `2.1`.
# Output: stakeholder-presentation-v2.1.docx# Footer: "Version 2.1 - Generated 2026-02-07"
Examples
Example 1: Basic Stakeholder Doc Export
Use this skill on `stakeholder-presentation.md`.
# Output:# โ stakeholder-presentation.docx created (47 pages, 2.4 MB)
Example 2: With Company Logo and PDF
Use this skill with a logo and PDF export enabled.
# Output:# โ stakeholder-presentation.docx (with Acme logo)# โ stakeholder-presentation.pdf
Example 3: Full Blueprint Export
Use this skill on `blueprint.md` with output path `architecture-blueprint.docx`.
# Output:# โ architecture-blueprint.docx (19 sections, 87 pages)
Quality Assurance
Before considering export complete, verify:
All sections from markdown are present in DOCX
All diagrams are embedded and visible
Table of contents has correct page numbers
Tables are formatted with headers
Code blocks use monospace font
Cover page has correct metadata
Approval section has signature fields
Headers/footers are present on all pages (except cover)
Page numbers start from correct page
Document is editable without errors
File size is reasonable (<10 MB)
Troubleshooting
Problem: Images are too large/small
Solution: Adjust max-width in Pandoc:
pandoc ... --metadata max-width=6in
Problem: Table of contents missing
Solution: Ensure --toc flag is used and H2/H3 headings exist
Problem: Code blocks lose formatting
Solution: Use --highlight-style=tango and monospace font in template
Problem: PDF export fails
Solution: Install required LaTeX packages or use LibreOffice conversion
