secondary-architecture-reviewer

Automate architecture review by analyzing OpenSpec, Git Diff, frontend, bff, backend, LangGraph, Tool, MCP, and security boundaries. The skill examines these areas to ensure compliance and outputs categorized findings to identify potential structural issues.

An automated architecture review systematically examines software project components including frontend, bff, backend, LangGraph, and MCP boundaries. It verifies security compliance and outputs categorized Blocker, Major, and Minor verdicts based on the codebase analysis.

Review security boundaries by executing an automated architecture review that scans Git Diff and project modules like backend and MCP. It identifies compliance issues and generates detailed reports highlighting potential security vulnerabilities.

Yes, you can analyze LangGraph and MCP components. The architecture review process specifically includes these components alongside frontend, bff, and backend layers to ensure comprehensive security and quality compliance across the software stack.

The best way to get detailed verdicts on software architecture compliance is to use an automated review tool that analyzes OpenSpec and Git Diff. It outputs categorized findings including Blocker, Major, and Minor issues based on your project's security boundaries.

A limitation of automated architecture review is that it relies on analyzing existing code and Git Diff. It may not detect undocumented design flaws or business logic errors outside the specified frontend, bff, backend, LangGraph, and MCP boundaries.