Diagram Forge
A text-to-diagram generation tool for architects and developers — turning structured descriptions into professional architectural diagrams without touching a drag-and-drop UI.
The Frustration
Architecture documentation degrades because diagrams are expensive to maintain. When the system changes, updating the diagram requires opening a tool, repositioning boxes, re-routing arrows, re-exporting. Most people just stop updating the diagram. Then the diagram lies.
Diagram Forge is built on a different premise: if diagrams are as easy to update as text, they stay current.
How It Works
Diagram Forge exposes an MCP server that integrates directly into Claude Code. Describe the architecture in natural language or structured format — “Show the AGF layered model with six layers and four governance viewpoints” — and get a rendered, styled diagram back. Iterate with natural language edits.
The tool handles prompt engineering, template selection, style application, and rendering. You focus on the architecture.
Why It Exists
I built Diagram Forge for my own work — the AGF diagrams, the ADF architecture models, the system maps across the Agentic Work System. The diagrams on this site are Diagram Forge outputs.
But the problem it solves isn’t unique to my work. Any team doing architecture documentation has the same friction. Diagram Forge is being prepared for community release as an open-source tool.
Aligned with the Mission
Diagram Forge is itself an artifact of the methodology it supports. It was built using ADF stage gates, governed with AGF principles in mind, and documented with the same rigor I’d apply to any enterprise system. It’s proof-of-practice as much as it’s a tool.
Status: Active development. Community release in preparation — needs distribution support and documentation pass before public launch.