architecture-drift-check

Detect architectural drift by comparing documented architecture against actual repository structure, file boundaries, and dependency patterns. This analysis flags boundary violations and path inconsistencies to prevent architectural decay after rapid feature development.

Architecture drift is the discrepancy between documented architecture and actual codebase structure, including file organization and dependencies. It causes architectural decay when different layers improperly interact or unexpected dependency changes occur during rapid development.

Check for boundary violations by scanning the repository for instances where different architectural layers or components improperly interact. This skill compares current dependency patterns against documented file boundaries to flag violations.

Yes, architecture drift detection requires reading ARCHITECTURE.md, STACK_PROFILE.md, INVENTORY.md, and AGENT_STATE.json to identify deviations. These files provide the documented structure needed to compare against actual repository shape and dependencies.

Yes, monitor dependency pattern changes by comparing repository shape like monorepo structures against documentation. This identifies unexpected changes in core frameworks or build assumptions and outputs findings to ARCHITECTURE_DRIFT_REPORT.md.

Prevent architectural decay by running regular drift detection checks that compare documented architecture against current codebase structure. This flags boundary violations and dependency changes, outputting findings to ARCHITECTURE_DRIFT_REPORT.md and DECISIONS.md for resolution.