review-feature-architecture

Feature architecture review analyzes implementation diffs or plan files to identify design risks, checking module boundaries, dependency direction, and blast radius. It applies strict scope control to prevent drifting into unfocused codebase analysis.

Checking a feature plan for integration issues uses Balanced Coupling analysis to evaluate boundary crossings and state flow. This process applies a structured coupling model to identify risky design decisions before implementation begins.

Validating architectural boundaries in a branch diff confirms that new services, interfaces, and cross-module dependencies are necessary, reversible, and operationally safe. It checks integration boundaries against intended feature scopes.

A multi-agent architecture review separates finding generation, validation, and improvement proposals so architectural issues are checked independently. This prevents self-validation bias common in standard code review processes.

An architecture review for a feature implementation diff is needed when you must assess whether new abstractions are justified and integration boundaries are preserved. It evaluates failure handling, test seams, and state flow within scoped feature work.