validate-architecture-spec

Validate architecture YAML artifacts against the six-artifact /arch contract.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill validate-architecture-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-architecture-spec
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/validate-architecture-spec
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill validate-architecture-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents enterprise delivery from proceeding when the architecture outputs do not satisfy the required six-artifact contract and their decision-manifest integrity rules, ensuring the derived architecture is structurally complete, consistent, traceable, and validation-ready.

Core Features & Use Cases

  • Validates six required architecture artifacts: refined quality-profile, systems-inventory, logical-architecture, physical-architecture, tech-stack, and technical-risks, including artifact non-emptiness.
  • Enforces logical and physical consistency: checks component shape, capability coverage, and cycle absence across both logical and physical graphs.
  • Verifies NFR and tech-stack discipline: ensures every NFR characteristic is delivered, pattern citations are valid and grounded, and tech-stack entries follow the required schema.
  • Guards risk quality and provenance: validates technical-risks structure and stage ordering, verifies refined quality-profile delta_log integrity, and ensures inventory provenance (including byte-for-byte KB grounding).

Quick Start

Ask the system to run validate-architecture-spec after tech-architect finishes producing the /arch derive artifacts to produce a validation-result.yaml file showing passed/failed status and all blocking violations.

Frequently Asked Questions about validate-architecture-spec

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

FAQPage Schema
How do I validate enterprise architecture artifacts for completeness and consistency?

To validate enterprise architecture artifacts, you run a validation check against the six-artifact contract to enforce structural completeness, logical and physical consistency, and traceability across discover, specify, design, build, and run stages. This produces a validation-result.yaml file showing passed or failed status and all blocking violations.

What is architecture validation in the enterprise SDLC?

Architecture validation in the enterprise SDLC is the process of blocking invalid architecture artifacts early by verifying that derived architecture YAML files satisfy decision-manifest integrity rules, NFR delivery mapping, and tech-stack schema discipline before delivery proceeds.

How do I check NFR mapping and pattern citation grounding in architecture files?

You check NFR mapping and pattern citation by running a validation that ensures every NFR characteristic is explicitly delivered and that all pattern citations are valid and grounded within the architecture output, preventing untraceable design decisions.

Can I detect cycles and verify capability coverage in logical and physical architecture graphs?

Yes, you can detect cycles and verify capability coverage by applying validation checks that enforce component shape consistency and cycle absence across both logical and physical architecture graphs to ensure structural integrity.

How do I verify inventory provenance and byte-for-byte KB grounding for architecture manifests?

You verify inventory provenance and byte-for-byte KB grounding by running a validation process that checks the systems-inventory artifact against knowledge base sources to ensure exact matching and traceable architecture origins.

What happens if technical risks structure or stage ordering fails validation?

If technical risks structure or stage ordering fails validation, the system blocks delivery by logging the violations in a validation-result.yaml file, ensuring that risk shapes and refined quality-profile delta log integrity are corrected before proceeding.