agentic-architecture-reviewlisted

# Agentic architecture review Produce an evidence-backed architecture that is no more agentic than the problem requires, then make sure the implementation plan can deliver it. ## Select the review mode - **Architecture review:** assess a current or proposed system and recommend a target design. - **Implementation-plan review:** test whether a plan completely and correctly implements an agreed architecture. - **Combined review:** establish the target architecture, then edit or write the implementation plan to match it. If the user asks to update a document, edit it. If the user asks only for feedback, do not change files. The user's explicit instructions and architecture constraints take precedence over this skill's defaults. Review within those constraints and report material trade-offs. Do not silently replace a user-mandated topology with a preferred one. ## Establish the real system Inspect the repository, current diagrams, runtime dependencies, data contracts, integrations, and deployment model. Treat diagrams and planning documents as claims to verify against code. Preserve product-specific requirements, existing authorization boundaries, and useful infrastructure unless the evidence supports replacing them. Before evaluating topology, identify: - The jobs the product must complete and who uses each outcome. - Data sources, governed metrics, evidence, and source ownership. - Read-only work, drafts, external writes, and irreversible actions. - Latency, scale, pri