Domäne
Documentation
Skill-Profil
Diagrams as code: Mermaid, PlantUML, D2, diagram versioning, auto-generation
Rollen
8
wo dieser Skill vorkommt
Stufen
5
strukturierter Entwicklungspfad
Pflichtanforderungen
27
die anderen 9 optional
Documentation
Docs-as-Code
17.3.2026
Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.
Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Game Designer | Creates simple game system diagrams: core loop flowcharts, mechanic interaction schemas, game content mind maps. Uses Miro, draw.io, or Figma to visualize game design ideas. Understands basic notations for describing game flows. | |
| Product Manager | Pflicht | Creates diagrams to visualize product concepts: user flows, wireframes, process maps. Uses Miro, Figma, draw.io. |
| Security Analyst | Understands the fundamentals of Diagramming: Mermaid, PlantUML, D2. Applies basic practices in daily work. Follows recommendations from the team and documentation. | |
| Technical Product Manager | Pflicht | Can read and create basic diagrams: flowcharts, sequence diagrams, user flows. Uses Miro, Lucidchart or draw.io for visualizing product processes. Understands UML notation at a basic level. |
| Technical Writer | Pflicht | Proficient with basic diagramming tools: draw.io, Lucidchart, Miro. Can create simple diagrams: flowcharts, sequence diagrams, mind maps. Knows basic notations: UML basics, flowcharts, network diagrams. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Engineering Manager | Uses Mermaid, PlantUML, or D2 to create process flows, org charts, and roadmap visuals. Understands when to use sequence vs. flowchart diagrams. Documents team workflows and communication paths independently. | |
| Game Designer | Creates detailed game system diagrams: state machines for AI behavior, progression flow diagrams, economic cycle schemas (sink/source). Visualizes dependencies between game systems. Uses UML to describe complex interactions. | |
| Product Manager | Pflicht | Creates comprehensive visualizations: service blueprints, system maps, impact maps. Uses diagrams for stakeholder communication. |
| Security Analyst | Applies Mermaid, PlantUML, or D2 to build threat model diagrams, basic attack trees, and network topology maps. Understands trade-offs between diagram formats for security documentation. Creates incident flow visuals independently. | |
| Technical Lead | Uses Mermaid, PlantUML, or D2 for technical design documents, component diagrams, and data flow visuals. Chooses appropriate diagram types for sequence and interaction modeling. Creates clear architecture sketches for the team independently. | |
| Technical Product Manager | Pflicht | Creates technical diagrams for product specifications: sequence diagrams for API interactions, data flow diagrams, state machines. Uses C4 model for documenting architecture at different levels. |
| Technical Writer | Pflicht | Creates complex technical diagrams: C4 model (all 4 levels), data flow diagrams, state machines, ER diagrams. Uses diagrams-as-code tools (Mermaid, PlantUML). Maintains visual consistency and diagram readability. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Engineering Manager | Pflicht | Designs comprehensive process flow systems and roadmap visualizations using Mermaid, PlantUML, or D2. Creates standardized org chart and communication templates. Mentors the team on effective diagramming for stakeholder presentations and cross-team alignment. |
| Game Designer | Designs comprehensive game system visualizations: full-game system diagrams, mechanic dependency graphs, data flow for live-ops pipeline. Creates interactive diagrams for presenting game design decisions to stakeholders. Documents architecture systematically. | |
| Product Manager | Pflicht | Masterfully visualizes complex concepts. Creates strategic visualizations: Wardley maps, ecosystem maps, opportunity landscapes. |
| Security Analyst | Pflicht | Designs production-grade threat modeling diagrams, multi-layer attack trees, and detailed network topology maps using Mermaid, PlantUML, or D2. Optimizes diagram complexity for incident response playbooks. Mentors analysts on security diagramming practices. |
| Solutions Architect | Pflicht | Designs production-grade C4 model diagrams, integration pattern visuals, and deployment architecture maps using Mermaid, PlantUML, or D2. Optimizes diagram layering for different stakeholder audiences. Mentors teams on architectural diagramming standards. |
| Technical Lead | Pflicht | Designs production-grade component diagrams, detailed data flow visuals, and sequence diagrams for complex systems using Mermaid, PlantUML, or D2. Optimizes technical documentation with layered diagram views. Mentors engineers on design documentation best practices. |
| Technical Product Manager | Pflicht | Designs comprehensive architectural diagrams for cross-team alignment: system context, container, and component levels. Creates dynamic diagrams for complex workflows. Defines visualization standards for teams. |
| Technical Writer | Pflicht | Designs visual language and diagramming standards for the project. Implements diagrams-as-code approach: Mermaid/PlantUML in Git, auto-generation from code, CI validation. Creates interactive diagrams for the developer portal (clickable architecture maps). |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Engineering Manager | Pflicht | Defines diagramming strategy for team communication, process documentation, and roadmap visualization. Establishes standards for org chart maintenance, workflow diagrams, and stakeholder reporting visuals. Conducts reviews of diagram quality across the product area. |
| Game Designer | Defines visual documentation standards for the game design team. Builds a diagram template library: economy flows, system architectures, player journey maps. Trains the team on effective visual communication of game design decisions. | |
| Product Manager | Pflicht | Standardizes visual standards for the division. Defines diagramming guidelines and templates. |
| Security Analyst | Pflicht | Defines diagramming strategy for threat modeling, attack surface visualization, and incident response documentation. Establishes standards for security architecture diagrams, network topology maps, and compliance visuals. Conducts reviews of security diagram accuracy and completeness. |
| Solutions Architect | Pflicht | Defines diagramming strategy for system architecture, C4 model adoption, and integration pattern documentation at the product level. Establishes standards for deployment diagrams, infrastructure visuals, and architecture decision records. Conducts reviews of architectural diagram consistency. |
| Technical Lead | Pflicht | Defines diagramming strategy for technical design documentation, component modeling, and data flow visualization at the team level. Establishes standards for sequence diagrams, API interaction visuals, and system boundary maps. Conducts reviews of technical diagram clarity and accuracy. |
| Technical Product Manager | Pflicht | Defines diagram standards and templates for the product division. Introduces diagrams-as-code approach (Mermaid, PlantUML) with versioning. Trains teams on effective visual communication of architectural decisions. |
| Technical Writer | Pflicht | Defines organizational standards for technical information visualization: notations, tools, color schemes, templates. Coordinates creation of unified system landscape diagrams combining knowledge from different teams. Trains on visualization techniques. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Engineering Manager | Pflicht | Defines organization-wide diagramming strategy for process documentation, cross-team communication visuals, and strategic roadmap presentation. Establishes enterprise standards for workflow and org structure diagrams. Mentors leads on effective visual communication for executive reporting. |
| Game Designer | Shapes visual communication culture at the studio level. Creates methodology for documenting complex game systems through diagrams. Defines enterprise tools and standards for game design visualization across multiple projects. | |
| Product Manager | Pflicht | Uses strategic visual tools for corporate-level communication. Visualizes portfolio strategy. |
| Security Analyst | Pflicht | Defines organization-wide diagramming strategy for enterprise threat modeling, security architecture documentation, and compliance reporting visuals. Establishes enterprise approaches to attack surface mapping and incident response diagramming. Mentors leads and architects on security visualization standards. |
| Solutions Architect | Pflicht | Defines organization-wide diagramming strategy for enterprise architecture, C4 model governance, and integration pattern standardization. Establishes enterprise approaches to deployment and infrastructure diagramming across all product lines. Mentors leads and architects on architectural visualization maturity. |
| Technical Lead | Pflicht | Defines organization-wide diagramming strategy for technical design documentation, component modeling standards, and data flow visualization patterns. Establishes enterprise approaches to sequence diagrams and system boundary mapping. Mentors leads and architects on technical diagramming excellence. |
| Technical Product Manager | Pflicht | Shapes enterprise approach to visual architecture documentation. Defines catalog of diagram types for different stakeholders. Integrates diagrams into developer portal and organization's architecture repository. |
| Technical Writer | Pflicht | Shapes technical knowledge visualization strategy at the company level. Defines tools and approaches for diagramming automation. Ensures visual documentation serves as living documentation reflecting the actual state of systems. |