validating-architecture-analysis

Validate architecture artifacts against contracts and cross-document consistency standards.

1|Updated Oct 29, 2025

Search Tags:#architecture #diagrams #validate #contracts #validation-report #cross-document

Ready to run

npx skills add https://github.com/tachyon-beep/hamlet --skill validating-architecture-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validating-architecture-analysis
Source: https://github.com/tachyon-beep/hamlet/tree/main/.claude/skills/axiom-system-archaeologist/skills/validating-architecture-analysis
Command: npx skills add https://github.com/tachyon-beep/hamlet --skill validating-architecture-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate architecture analysis artifacts (subsystem catalogs, diagrams, and reports) against contract requirements and cross-document consistency standards, producing actionable validation reports with clear approval or revision status.

Core Features & Use Cases

Contract Compliance: Validate catalogs, diagrams, and final reports against their formal contracts to surface missing sections and inconsistencies.
Cross-Document Consistency: Ensure catalog dependencies align with diagram arrows and final report references across documents.
Output & Governance: Produce structured Validation Reports suitable for review and archival.

Quick Start

Prepare your artifacts (02-subsystem-catalog.md, 03-diagrams.md, 04-final-report.md) and run the validation workflow to generate a workspace temp validation report.

Frequently Asked Questions about validating-architecture-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate architecture diagrams against subsystem catalogs?▼

Architecture diagrams are validated against subsystem catalogs by checking cross-document consistency, ensuring catalog dependencies align with diagram arrows, and producing a detailed validation report with traceable findings and line references.

What is cross-document consistency validation for architecture artifacts?▼

Cross-document consistency validation checks architecture artifacts like subsystem catalogs, diagrams, and final reports to ensure dependencies and references align across documents, generating a structured report with an APPROVED or NEEDS_REVISION status.

How do I generate an architecture validation report with approval status?▼

Generate an architecture validation report by running the validation workflow on prepared artifacts like 02-subsystem-catalog.md and 03-diagrams.md, which outputs a detailed report in workspace temp with clear APPROVED or NEEDS_REVISION status and actionable fixes.

Can I check contract compliance for architecture final reports automatically?▼

Final reports are checked against formal contracts automatically to surface missing sections and inconsistencies, providing a structured validation report suitable for review and archival with actionable fixes and line references.

What file formats do I need for architecture artifact validation?▼

Architecture artifact validation requires markdown files including 02-subsystem-catalog.md, 03-diagrams.md, and 04-final-report.md, which are validated against contract requirements to produce a structured validation report in workspace temp.

Why does my architecture validation report show NEEDS_REVISION status?▼

A validation report shows NEEDS_REVISION status when architecture artifacts fail contract compliance or cross-document consistency checks, providing traceable findings with line references and actionable fixes to address missing sections or misaligned dependencies.