About architecture-validation
architecture-validation dynamically checks whether a codebase follows architectural decisions recorded in plan files. It is intended for development and architecture reviews, and adapts to different project structures while reporting gaps and drift.
Key features
- 01Discover plan files in `plans/`
- 02Extract architectural requirements
- 03Compare plans with the codebase
- 04Check compliance and architecture drift
- 05Report omissions, deviations, and extras
Use cases
- 01Check architecture drift after development
- 02Verify that design decisions were implemented
- 03Identify requirements still missing
- 04Confirm boundaries after refactoring
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ d-o-hub/ rust-self-learning-memory --skill architecture-validationAfter installing, type/architecture-validationin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
compliance.mddimensions.mdextraction.mdself-learning.mdworkflow.mdDetails
From the project READMEArchitecture Validation Skill
Dynamically validate that the implemented codebase matches architectural decisions documented in plan files.
Quick Reference
- Dimensions - What gets validated (components, dependencies, APIs, etc.)
- Workflow - Step-by-step validation process
- Extraction Patterns - How to extract architectural elements from plans
- Compliance - Compliance levels and report format
- Self-Learning - Continuous improvement framework
Purpose
Generic, adaptive framework that:
- Discovers all plan files in
plans/directory - Extracts architectural requirements dynamically
- Validates implementation compliance
- Reports gaps, drift, and violations
Key Principle: Be architecture-agnostic. Work with ANY project structure.
When to Use
- Validating implementation matches planning documents
- Checking for architecture drift after development
- Ensuring design decisions are followed
- Identifying missing implementations
- Preparing for architecture reviews
- Verifying refactoring didn't break boundaries
Validation Workflow
- Discover - Find all plan files
- Extract - Pull architectural elements
- Analyze - Compare vs codebase
- Validate - Check compliance
- Gap Analysis - Identify missing/drift/extra
- Report - Generate comprehensive report
See workflow.md for detailed phases and dimensions.md for validation categories.
Comments
Markdown supported