speckit-architecture-guard-architecture-review

Architecture drift is detected by performing an evidence-based review that validates implementation alignment against architecture specs, plans, and governance constitutions. This process automatically scopes analysis to changed files and cites concrete implementation evidence like file paths and line numbers for each violation.

Evidence-based architecture review is a validation method that produces structured reports where each violation cites concrete implementation evidence, such as file paths, line numbers, or observable patterns. It explicitly notes critical absences and converts confirmed violations into actionable refactor tasks with priorities.

Yes, you can apply framework-agnostic governance checks for boundary integrity, contract fidelity, and layering independent of your tech stack. It optionally applies framework-aware vocabulary when presets exist and can run SonarLint-based checks to correlate code quality risks with architecture violations.

Refactor tasks are generated by converting confirmed architecture violations into non-blocking, actionable items with priorities and suggested fixes. This occurs automatically as part of the structured output during an architecture review that checks implementation alignment against governing constitutions.

No, architecture review requires strict read-only behavior during analysis. It performs governance checks using progressive context loading and changed-file detection to validate implementation alignment without modifying your source files.