Validate an architecture document (the {app}_Architecture.md produced by the Senior Cloud Architect agent) against a hard Definition of Done: required sections, the five required diagrams, well-formed Mermaid, the seven explanation parts per diagram, and the repository copy conventions. Use when producing, reviewing, or finishing an architecture document, or whenever you need to confirm a Mermaid-based architecture deliverable is complete and will render before presenting it.
Instalación
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Validate an architecture document (the {app}_Architecture.md produced by the Senior Cloud Architect agent) against a hard Definition of Done: required sections, the five required diagrams, well-formed Mermaid, the seven explanation parts per diagram, and the repository copy conventions. Use when producing, reviewing, or finishing an architecture document, or whenever you need to confirm a Mermaid-based architecture deliverable is complete and will render before presenting it.
argument-hint
the architecture markdown file to validate, for example UBB_Platform_Architecture.md
Architecture Doc
The quality gate for architecture documents in this workspace. It turns the Senior Cloud Architect's Definition of Done into an executable check so an architecture deliverable cannot ship incomplete or with broken Mermaid, which is the main source of rework.
Pair this with the deploy-managed architecture workflow: the responsible agent designs and writes {app}_Architecture.md, then runs this gate before presenting.
When to use
After producing an architecture document, before presenting it.
When reviewing or finishing someone else's architecture markdown.
Whenever you need to confirm the Mermaid diagrams will render and every diagram is fully explained.
What it enforces
Required sections: Executive Summary, System Context, Component Architecture, Deployment Architecture, Data Flow, Risks and Mitigations.
The five required diagrams are present: System Context, Component, Deployment, Data Flow, Sequence.
Well-formed Mermaid: every block is fenced and non-empty, declares a known diagram type (graph, flowchart, sequenceDiagram, erDiagram, stateDiagram-v2, and so on), has balanced brackets, and has edges or messages where the type needs them.
The seven explanation parts appear in each diagram's section: Overview, Key Components, Relationships, Design Decisions, NFR Considerations, Trade-offs, Risks and Mitigations.
Conventions: no em dashes, "GitHub Copilot" never abbreviated to bare "Copilot", and no unfilled template placeholders ({app}, [Diagram], TODO, TBD).
Workflow
Write or update the architecture document as {app}_Architecture.md.
It prints warnings (review) and errors (must fix), and exits non-zero if any error is found.
Fix every reported error, then rerun until it passes. Do not present a document that fails the gate.
Record the result at the end of the document as a short "Validation" note.
Override the minimum diagram count only when justified: --min-diagrams 6.
Notes
The script is standard-library Python and self-contained; no install needed.
It cannot fully render Mermaid, so it uses high-signal structural checks. If a diagram is very complex, simplify it rather than risk a render error.
Numbers in an architecture document (NFR targets, costs) must be sourced or labeled as assumptions; the gate flags conventions, not factual accuracy, so keep the data integrity rule yourself.
