Shift from creating visually-polished documents for humans to producing structured, machine-readable plans. This allows team members' agents to parse, summarize, and act on the information, making collaboration faster. The focus becomes the quality of the plan, not its presentation.

The debate over using HTML versus Markdown to communicate with AI agents reveals a deeper shift. The primary job of a knowledge worker is no longer to complete a task, but to create the optimal conditions, context, and scaffolding for an AI agent to perform the work effectively.

The use of rich HTML artifacts extends beyond code plans to internal communications. By having an AI read Slack messages and generate a weekly status update in HTML, communication becomes more engaging and consumable for managers. This is a practical application of AI to improve the effectiveness of routine internal reporting.

Move beyond generating plain text by prompting AI to build complete, individual HTML artifacts for email campaigns. By specifying brand styles, you can get production-ready code that can be directly imported into an email service provider, significantly reducing manual design and coding work for marketing teams.

Traditional file formats like PowerPoint and Word documents are difficult for LLMs to parse. The future of work involves creating artifacts, like SOPs or presentations, in formats such as HTML that are easily understood by both humans and AI, improving workflow automation and knowledge transfer.

HTML excels in the new "agent staging" paradigm because its native features (tabs, color-coding, expandable sections) can encode a project's "mixed doneness." This visually distinguishes between locked requirements, open exploratory areas, and provisional decisions, calibrating the agent's autonomy more effectively than plain text.

Standard file formats like .docx and .pptx are filled with complex code that LLMs struggle to parse. To build effective AI workflows, companies must create deliverables in formats that are both human-readable and AI-friendly. HTML is a prime example, as it is visually appealing for people and easily ingested by AI.

Instead of relying on scattered design docs or linking a repo, generate a "living design system" as a single HTML file. This artifact visually represents colors, typography, and components. It's easily passed to an AI agent in any new project, providing a compressed, comprehensive, and visual understanding of design constraints.

When building multi-agent systems, tailor the output format to the recipient. While Markdown is best for human readability, agents communicating with each other should use JSON. LLMs can parse structured JSON data more reliably and efficiently, reducing errors in complex, automated workflows.