Mermaid Diagramming Engine

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Generates syntactically valid, semantically precise Mermaid diagrams for discovery deliverables. Every diagram earns its place — no decorative visuals. Each diagram must compress complexity into clarity, replacing paragraphs of prose with a single visual that a reader grasps in seconds [EXPLICIT]

When to Use

• Any discovery deliverable needs architectural, flow, or relationship visualization
• A concept is better understood visually than textually
• Cross-references between components, stakeholders, or phases need mapping
• Decision trees, timelines, or state machines need representation

When NOT to Use

• The diagram would merely repeat what the text already says clearly
• Data is better represented as a table (metrics, scores, comparisons)
• The audience won't have Mermaid rendering capability (use ASCII fallback)

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: · Cannot generate raster images (PNG/SVG) — output is Mermaid code only · C4 diagrams use Mermaid's C4 extension (may not render in all contexts) · Complex diagrams (>20 nodes) req. [EXPLICIT]
• Casos borde: · If source data is insufficient for a meaningful diagram → skip diagram, note gap · If two diagram types are equally valid → prefer the one with fewer nodes · If diagram would con. [EXPLICIT]
• Supuestos: · Target renderers support Mermaid v10+ syntax · Readers have basic familiarity with flowchart/diagram conventions · Diagrams supplement text, never replace it entirely. [SUPUESTO]
• Trade-off: Decision Enables Constrains When to Use --- --- --- --- Max 20 nodes Readability, quick comprehension Cannot show full system in one view Always — split com. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.