architecture-reviewer-agent

An architecture boundary and ownership review evaluates system boundaries, coupling, sequencing, and contracts to identify misplaced responsibilities. It verifies that ownership scopes prevent overlapping duties and gaps, reducing release risk through actionable corrective recommendations.

Review service coupling and contracts by assessing sequencing clarity and boundary definitions to expose design risks. This process identifies ownership gaps and provides concrete recommendations for architectural improvements to tighten service boundaries.

Yes, you can use this for plugin ownership validation and design reviews. It evaluates whether responsibilities are placed in the correct scope, enforcing stronger boundary definitions and verifying ownership to prevent overlapping plugin responsibilities.

You need an architectural critique when a task involves design risks from unclear ownership or boundary gaps. It assesses coupling and contract clarity to validate that system responsibilities are correctly scoped and placed within the right boundaries.

The best way to identify ownership gaps is by evaluating boundaries, coupling, and contracts across the service architecture. This approach outlines specific ownership gaps and suggests boundary corrections to ensure clear, actionable governance.

Relying solely on coupling analysis limits architecture reviews by missing boundary, ownership, and contract clarity issues. A comprehensive review must also evaluate sequencing and design risks to provide actionable recommendations for corrective governance.