Skip to main content
Omni Architect supports 8 different Mermaid diagram types, each serving a specific purpose in visualizing product logic. Configure which diagrams to generate using the diagram_types parameter.

​
Configuration

diagram_types:
  - flowchart
  - sequence
  - erDiagram
  - classDiagram
  - stateDiagram
  - C4Context
  - journey
  - gantt

​
Default Diagram Types

If not specified, Omni Architect generates these 5 diagram types by default: 
diagram_types:
  - flowchart
  - sequence
  - erDiagram
  - stateDiagram
  - C4Context

​
Available Diagram Types

​
1. Flowchart (flowchart)

Purpose: Visualize business flows and process logic PRD Mapping: Extracted from flows section in parsed PRD Use Cases:
  • User checkout process
  • Authentication flows
  • Product search and filtering
  • Multi-step forms
Example Output:

​
2. Sequence Diagram (sequence)

Purpose: Show interactions between actors and system components PRD Mapping: Extracted from user_stories section in parsed PRD Use Cases:
  • API request/response flows
  • User-system interactions
  • Service-to-service communication
  • Authentication sequences
Example Output:

​
3. ER Diagram (erDiagram)

Purpose: Model data entities and their relationships PRD Mapping: Extracted from entities section in parsed PRD Use Cases:
  • Database schema design
  • Domain model visualization
  • Entity relationships
  • Data architecture planning
Example Output:

​
4. Class Diagram (classDiagram)

Purpose: Visualize object-oriented class structures and relationships PRD Mapping: Extracted from entities section with emphasis on behavior and methods Use Cases:
  • Object-oriented design
  • Class hierarchies and inheritance
  • Service layer architecture
  • Domain-driven design patterns
Example Output:

​
5. State Diagram (stateDiagram)

Purpose: Represent state machines and feature states PRD Mapping: Extracted from features.states in parsed PRD Use Cases:
  • Order status workflows
  • Feature flags and states
  • User lifecycle management
  • Application state transitions
Example Output:

​
6. C4 Context Diagram (C4Context)

Purpose: High-level architectural overview PRD Mapping: Extracted from system_overview in parsed PRD Use Cases:
  • System context and boundaries
  • External integrations
  • Microservices architecture
  • Platform overview
Example Output:

​
7. Journey Diagram (journey)

Purpose: Map user journey and experience PRD Mapping: Extracted from personas + journeys in parsed PRD Use Cases:
  • User experience mapping
  • Customer journey visualization
  • Touchpoint analysis
  • Emotion and satisfaction tracking
Example Output:

​
8. Gantt Chart (gantt)

Purpose: Show roadmap and feature dependencies over time PRD Mapping: Extracted from dependencies + timeline in parsed PRD Use Cases:
  • Project timeline planning
  • Feature dependency tracking
  • Sprint planning
  • Milestone visualization
Example Output:

​
PRD to Diagram Mapping

PRD ElementDiagram TypePurpose
flowsflowchartVisualize business flows
user_storiessequenceShow actor-system interactions
entitieserDiagramModel data and relationships
features.statesstateDiagramRepresent state machines
system_overviewC4ContextHigh-level architecture
personas + journeysjourneyUser journey maps
dependencies + timelineganttRoadmap and dependencies

​
Selective Generation

You can generate only specific diagram types based on your needs:

​
Architecture Focus

diagram_types:
  - erDiagram
  - C4Context

​
User Flow Focus

diagram_types:
  - flowchart
  - sequence
  - journey

​
Project Planning Focus

diagram_types:
  - gantt
  - stateDiagram

​
Automatic Skipping

If your PRD doesn’t contain relevant data for a diagram type, Omni Architect automatically skips it:
Example: If your PRD has no user stories, sequence diagrams will be automatically skipped even if included in diagram_types.

​
Best Practices

Begin with the default 5 diagrams (flowchart, sequence, erDiagram, stateDiagram, C4Context) which cover most product logic validation needs.
Include journey when working on user experience-focused features or when presenting to stakeholders who value customer journey visualization.
Add gantt when your PRD includes timeline information or when coordinating with project managers who need visual roadmaps.
Always include erDiagram as it forms the foundation for data consistency across all other diagrams.

​
Next Steps

Validation Modes

Learn how diagrams are validated before Figma generation

Design Systems

Configure how diagrams are transformed into Figma assets

Build docs developers (and LLMs) love

Get started for freeTalk to us