plan-review-architecture

Identify architectural risks by analyzing component boundaries, data flow, dependencies, and security boundaries within a confirmed scope. Structured evaluation surfaces coupling, API contracts, rollout strategies, observability gaps, and failure scenarios early to produce a prioritized risk and action list.

Scope-focused architecture design review evaluates only the architecture affected by an agreed scope, aligning with local patterns and existing boundaries. It is needed when planning a new module or rollout to validate component ownership, data flow, and security boundaries before implementation.

Audit data flow and security boundaries by applying structured evaluation to dependencies, API contracts, and rollout strategies. This analysis identifies coupling and failure scenarios, returning a prioritized list of findings with evidence references and recommended mitigations to de-risk plans.

Yes, architecture analysis checks observability and coupling by assessing component boundaries and failure modes for the confirmed scope. It ensures guardrails and actionable mitigations are clearly described, providing concrete deliverables with evidence references before implementation begins.

De-risk architecture plans by running a scope-focused evaluation that assesses only the architecture affected by the agreed scope. This avoids validating beyond scope while identifying risks in dependencies, security boundaries, rollout plans, and observability to surface actionable mitigations early.

Architecture validation often misses failure scenarios and observability gaps when evaluation extends beyond the agreed scope without structured analysis. Applying targeted review to component boundaries, data flow, and dependencies ensures guardrails and evidence references are clearly described.