MarsDawn
Hand them the PDF, not the Markdown.
An agent finishes a document, you review and revise it, and then someone outside engineering needs to read it too — a manager, a client, someone on another team. They don't need to know what ## or a pipe table means. Export to PDF and hand them that instead.
Export the reviewed document to PDF and send that file. It opens in anything, needs no Markdown knowledge and no install, and looks the way you saw it in the preview — diagrams, tables and formatting included.
Why not just send the .md file
A raw .md file opened in a plain text editor shows the marks, not the page: # for a heading, ** around bold text, a fenced block for a Mermaid diagram that isn't drawn. Someone who doesn't write Markdown doesn't read any of that as intended, and asking them to install a viewer first is asking a lot for one document.
Why not a screenshot
A screenshot freezes one screen's worth of a document that may run to several pages, can't be searched or selected, and reads worse once it's compressed and forwarded a few times. A PDF keeps the text, the diagrams and the page breaks intact, at any length.
What a PDF gets you
- Opens in whatever the recipient already has — Preview, a browser, Acrobat, their phone — no Markdown tool required.
- Mermaid diagrams are drawn in, not left as code; code blocks keep their highlighting.
- Page breaks are chosen so a heading doesn't land alone at the bottom of a page, and a table or diagram isn't split across two.
- The same file whether it came from the MarsDawn app or the free command line — see Markdown to PDF for that walk-through.
Next
- The themes and layouts the export can come from: preview themes and PDF export.
- Export from a script or an agent instead of the app: marsdawn for agents.
- Why a person still needs to read the document first: the case for review.