DOCX

Build or edit a Word document and write it into the task directory (e.g. acme_memo/acme_q3_memo.docx). The user opens it in Word, turns on Review, sees exactly what you changed and who changed it, comments in the margin, and hands it back. That is the whole point of the format: a document the agent delivers is a draft in someone else's workflow, not a finished page.

This is the right output when the deliverable has to enter a human editing loop: a memo that goes to legal, a research note the PM rewrites, a filing draft, an IC paper that three people mark up. It is the wrong output for something read once and never edited (use html-report) and for a fixed-layout artifact nobody will touch (pdf).

User preferences override these defaults. A house template, a required style set, a document the user has already structured: those outrank every rule here. The rules below are for when nothing has been specified.

Decide: Which Output?

Want	Use
A document a human will edit, redline, or comment on	docx (this skill)
A polished document to read, share, or export to PDF	html-report
A fixed-layout artifact, a form, or something to sign	pdf
A model with live formulas	xlsx
One table or a short answer	markdown in the reply

Workflow