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.

AI development tools can be "resistant," ignoring change requests. A powerful technique is to prompt the AI to consider multiple options and ask for your choice before building. This prevents it from making incorrect unilateral decisions, such as applying a navigation change to the entire site by mistake.

Unlike screen-reading bots, web agents can leverage HTML's declarative nature. Tags like `<button>` explicitly state the purpose of UI elements, allowing agents to understand and interact with pages more reliably and efficiently. This structural property is a key advantage that has yet to be fully realized.

The simple, text-based structure of Markdown (.md) files is uniquely suited for both AI processing and human readability. This dual compatibility is establishing it as the default file format for the AI era, ideal for creating knowledge bases and training documents that both humans and agents can easily use.

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.

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.

In this software paradigm, user actions (like button clicks) trigger prompts to a core AI agent rather than executing pre-written code. The application's behavior is emergent and flexible, defined by the agent's capabilities, not rigid, hard-coded rules.

Instead of prompting for code line-by-line, "Plan Mode" has the AI agent generate a detailed plan in a markdown file first. The user reviews and modifies this plan like a spec document, elevating their role from coder to architect before the AI executes the build.