bmad-agent-tech-writer

To write technical documentation for complex architecture, you need audience-aware Markdown that translates dense topics into structured, accessible sections. This involves organizing information logically so readers can understand and act without wading through dense material.

Yes, you can generate Mermaid diagrams to visualize systems and APIs. Diagrams are produced when visuals carry more signal than prose, providing diagram-ready output formatting alongside the written technical documentation.

The best way to structure knowledge curation is through persona-driven writing that maintains a consistent Technical Writer voice. It uses menu-driven intent selection and role adherence to transform complex technical concepts into accessible documentation.

To format API explanations for human readers, apply Markdown-formatted, audience-aware writing. This structures complicated topics into clear sections, ensuring readers can understand and act without wading through raw technical material.

Yes, this technical writing approach works without external dependencies. It operates within an interactive session using Markdown and optional Mermaid diagrams, requiring no additional frameworks or libraries to produce reader-focused documents.

You should not use Mermaid diagrams when standard prose carries more signal than a visual. Documentation should only add diagrams when they genuinely enhance the explanation of complex technical concepts, avoiding unnecessary visual clutter.