/skill-doc-delivery

name: skill-doc-delivery
description: "Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables"
disable-model-invocation: true

> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex. > Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands. > Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. > For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.

Document Delivery for Knowledge Workers

Convert knowledge work outputs from markdown to professional office documents (DOCX, PPTX, XLSX).

Overview

This skill helps you transform knowledge work results into polished, deliverable documents:

• **After empathize** → Export personas to PPTX decks or requirements to DOCX specs
• **After advise** → Convert strategic analysis to PPTX presentations or DOCX business cases
• **After synthesize** → Generate literature reviews as DOCX academic format or PDF

Prerequisites Check

Inspect the current session's advertised skills for the requested format. A standalone `pptx`, `docx`, `xlsx` or `pdf` skill, or a namespaced equivalent, is sufficient. The `document-skills` plugin is one possible source. Files on disk do not establish that a skill is enabled for this session.

Set `OCTO_ROOT` to the installed Octopus root identified by this loaded skill or the host's plugin-root metadata. Verify that it contains `scripts/helpers/document-renderer.py`, then run it with `--format FORMAT` and one `--available-skill NAME` for each advertised skill. Pass `--renderer NAME` and `--template PATH` when explicitly requested. Quote each argument as data, including every advertised skill name. Use the returned `skill` and `template` for conversion. The helper also reads saved choices from `~/.claude-octopus/document-renderers.json`. See `docs/DOCUMENT-RENDERERS.md`.

If the selected skill is unavailable, discovery is ambiguous or the template is missing, report that specific problem. Do not replace a saved or explicit choice silently. Offer installation guidance only when the needed capability is absent; do not install plugins automatically.

Format Recommendations by Workflow

Empathize Workflow → UX Research Outputs

**Best for PPTX (PowerPoint):**

• Persona decks for stakeholder presentations
• Journey map visualizations
• Research synthesis highlights
• Executive summaries

**Best for DOCX (Word):**

• Detailed persona documentation
• Research requirements specifications
• Interview transcripts and analysis
• User story documentation

Advise Workflow → Strategic Analysis

**Best for PPTX (PowerPoint):**

• Strategy presentations for leadership
• Market analysis decks
• Competitive intelligence briefs
• Business case pitch decks
• Board presentations

**Best for DOCX (Word):**

• Comprehensive business cases
• Strategic recommendations reports
• Market research documentation
• Financial analysis reports

Synthesize Workflow → Research Synthesis

**Best for DOCX (Word):**

• Literature review papers
• Research synthesis reports
• Academic research documentation
• Annotated bibliographies
• Technical white papers

**Best for PDF:**

• Final publications
• Archival versions
• Shareable research reports

Conversion Guidelines

Step 1: Locate Source Markdown

Knowledge work outputs are stored in:

~/.claude-octopus/results/

List recent outputs:

ls -lht ~/.claude-octopus/results/ | head -10

Step 2: Choose Format Based on Purpose

Ask yourself:

• **Presenting to stakeholders?** → PPTX (visual, concise)
• **Comprehensive documentation?** → DOCX (detailed, structured)
• **Final publication?** → PDF (archival, unchangeable)
• **Data/frameworks?** → XLSX (tables, calculations)

Step 3: Invoke the selected renderer

Invoke the resolved skill with the source markdown, requested format and selected template. For slides with approved materials, include the approved slide skeleton, visual callout plan and appendix list. Otherwise, pass the source markdown without implying that an outline or slide materials were approved. Follow that skill's supported-format, authentication, publication and sharing rules. Report its actual artifact path or native deck URL, and report failures without claiming a completed conversion.

When the default document-skills renderers are selected, their capabilities are:

**For DOCX (Word):**

Use the /document-skills:docx skill to convert markdown to Word format.
Supports headings, lists, tables, and formatting.

**For PPTX (PowerPoint):**

Use the /document-skills:pptx skill to convert markdown to PowerPoint.
Each ## heading becomes a slide, bullet points auto-format.

**For PDF:**

Use the /document-skills:pdf skill to generate PDF documents.
Ideal for final deliverables and archival.

Step 4: Apply Professional Styling

After conversion, consider:

• **Consistent formatting** - Use heading styles, bullet hierarchies
• **Visual hierarchy** - Important points first, details later
• **Brand alignment** - Add logos, colors, fonts if needed
• **Readability** - Break up long paragraphs, use white space

Common Conversion Patterns

Pattern 1: Single Workflow → Single Document

User ran one workflow, wants one document:

User: "Export my latest synthesis to a Word document"

1. Check ~/.claude-octopus/results/ for most recent .md file
2. Identify it's from synthesize workflow
3. Recommend DOCX for academic report format
4. Invoke the resolved DOCX renderer with the selected template
5. Save to appropriate location

Pattern 2: Multiple Sections → Presentation

User wants to create a deck from research:

User: "Create a PowerPoint from this research"

1. Locate the research markdown
2. Identify key sections (## headings)
3. Invoke the resolved presentation renderer with the s