Use cases

Where mdd fits: agent context files, code comments, data pipelines, runbooks, threat models, design docs, sequence flows, and tutorials — worked examples of diagrams your agent draws and you review.

9 pages · 4 groups

Agent context

AGENTS.md architecture maps

An architecture map in your agent context file: ASCII for humans, JSON ground truth for the agent.

Multi-agent orchestration maps

Agent hand-offs, tool wiring, and memory flow — documentation the agents themselves can update.

In the codebase

Diagrams in code comments

Header-comment state machines and layouts, computed from JSON and spliced behind // or #.

Data pipeline lineage maps

A curated lineage map your agent keeps current as pipeline models change.

Operations

Runbook flowcharts

Decision flows and failure maps readable in any terminal, drafted and updated by your incident tooling.

Written docs

Design docs, RFCs & ADRs

RFC and ADR system diagrams that stay legible in diffs across every revision round.

ASCII sequence diagrams

Auth flows and call chains as plain text: message order in the JSON is the layout.

Docs-as-code threat models

Data-flow diagrams with trust boundaries, drafted from the code and reviewed in the diff.

Tutorials & conceptual docs

Conceptual diagrams that survive every downstream medium: docs site, README, PDF, chat.