c4-model

C4 architecture documentation is generated by processing input codebases through specialized agents that analyze component boundaries and container mappings. The workflow produces level-specific Markdown outputs and Mermaid diagrams across Context, Container, Component, and Code levels.

Automating C4 model documentation is best achieved by running a workflow that uses reference templates and specialized agents to analyze codebases. This generates repeatable, structured Markdown documentation and Mermaid diagrams across all four C4 levels.

Yes, you can generate only the Container level diagram without documenting the entire system because the workflow supports optional level selection. This allows you to target specific C4 levels individually rather than producing end-to-end documentation.

Yes, you need to define component boundaries before generating C4 documentation because the workflow requires these mappings as input. Providing component boundaries and reference templates ensures the generated architecture diagrams are consistent and actionable.

C4 architecture diagrams are output in Mermaid diagram format embedded within Markdown files for stakeholder discussions. This format allows architecture dependencies and system structures to be visualized directly in version-controlled documentation.

You should not use automated C4 model generation when your codebase lacks clear component boundaries or container mappings, as the workflow requires these inputs to produce consistent documentation. Without defined reference templates, the generated diagrams may lack actionable architectural context.