Help us improve
Share bugs, ideas, or general feedback.
From aidoc-flow
Generates and manages Mermaid architecture diagrams as separate traceable files linked to parent SDD documents (BRD, PRD, ADR, SPEC, IPLAN). Handles creation, inline migration, validation, and SVG rendering.
npx claudepluginhub vladm3105/aidoc-flow-framework --plugin aidoc-flowHow this skill is triggered — by the user, by Claude, or both
Slash command
/aidoc-flow:charts-flowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate and maintain Mermaid architecture diagrams for SDD documents. Diagrams
Guides creation of syntactically valid Mermaid diagrams for PRDs, specs, roadmaps, and presentations by selecting from 15 types, following syntax rules, and validating. Includes PM examples and selection guide.
Routes Mermaid diagram requests to type-specific guides (sequence, activity, ER, architecture); validates .md files, renders .mmd to SVG, architects from codebases.
Provides Mermaid templates for flowcharts, sequence diagrams, class diagrams, ER diagrams, and C4 models for technical documentation.
Share bugs, ideas, or general feedback.
Generate and maintain Mermaid architecture diagrams for SDD documents. Diagrams
live in separate diagrams/ files next to their parent document — keeping the
parent lean to render — and stay traceable back to that parent through a stable
diagram ID and a back-reference link.
This is the single diagram skill for the plugin: all Mermaid generation, validation, and SVG rendering lives here.
Use charts-flow when:
mermaid block into a separate diagram file.Do not use it for simple tables/lists (use markdown), tiny diagrams that render fine inline, or non-architecture charts (Gantt, pie) that fall outside the SDD diagram contract.
Create a new diagram
PRD-01) and locate
its folder.diagrams/ beside the parent if absent, and write
{PARENT-ID}-diag_{description}.md containing a Document Control block
(parent link, diagram type, dates), an overview, the mermaid block, and a
References section linking back to the parent.mmdc CLI if available, otherwise Mermaid Live), validate the
syntax, and embed the SVG preview in the parent inside a collapsible
<details> block with a link to the diagram file.Migrate inline diagrams
mermaid blocks, move each into its own diagram file
(numbering multiples), then replace the original block with the SVG preview
plus a reference link, preserving document flow.Supported types: flowchart/graph, sequence, class, state, component, and deployment. Each diagram file follows the same Document Control + References structure so cross-references resolve in both directions.
Diagram contract (per layer): diagrams attach to the layers that own visual
models — BRD (C4 L1 + DFD L1), PRD (C4 L2 + DFD L2 + key sequence), ADR
(decision sequences), SPEC (C4 L3 + DFD L3). Use the @diagram: tags the layer
template specifies and follow framework/governance/DIAGRAM_STANDARDS.md.
Quality gates: diagram file in the correct diagrams/ folder; name matches
{PARENT-ID}-diag_{description}.md; Document Control with parent back-link;
valid Mermaid syntax; SVG embedded; all cross-references resolve; SVG < 1 MB.
framework/governance/DIAGRAM_STANDARDS.mdframework/governance/ID_NAMING_STANDARDS.mdframework/layers/01_BRD/BRD-TEMPLATE.yaml,
framework/layers/02_PRD/PRD-TEMPLATE.yaml,
framework/layers/05_ADR/ADR-TEMPLATE.yaml,
framework/layers/06_SPEC/SPEC-TEMPLATE.yaml../adr-roadmap/SKILL.md