architect-review

Reviews system architecture for scalability, security, and pattern compliance.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill architect-review-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-review
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/TongQuan/skills/architect-review
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill architect-review-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It helps teams evaluate architectural decisions before they become costly mistakes, catching design flaws, anti-patterns, and scalability risks in distributed systems early. ## Core Features & Use Cases - Architecture Review: Assesses designs against clean architecture, microservices, DDD, and event-driven patterns with a High/Medium/Low impact rating. - Quality Attribute Analysis: Evaluates reliability, security, performance, maintainability, and cost characteristics of proposed systems. - Decision Documentation: Produces Architecture Decision Records and concrete refactoring recommendations with tradeoffs. - Use Case: Before merging a proposal to split a monolith into microservices, ask for a review of service boundaries, data isolation, and distributed transaction handling to identify risks and next steps. ## Quick Start Review this microservice design for proper bounded context boundaries and identify architectural risks.

Frequently Asked Questions about architect-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a microservices architecture design?▼

Gather the system context, goals, and constraints, then evaluate service boundaries against domain-driven design bounded contexts. Assess data isolation, communication patterns, and resilience mechanisms like circuit breakers, and document findings with an impact rating.

What should an architecture review checklist include?▼

Cover pattern compliance, quality attributes like reliability and scalability, security posture, and deployment pipeline maturity. Also verify documentation such as C4 diagrams and Architecture Decision Records exist for significant decisions.

When should I not request a full architecture review?▼

Skip it for minor changes local to a single module or small code reviews without architectural impact. A full review also adds little value when you lack system context or requirements to assess the design against.

How do I evaluate event-driven architecture trade-offs?▼

Compare event sourcing and CQRS benefits like auditability and decoupling against added complexity in consistency and debugging. Assess whether saga or outbox patterns are needed for distributed transactions before recommending adoption.

Can architecture reviews assess security and compliance?▼

Yes, reviews cover zero trust models, OAuth2 and JWT token handling, encryption at rest and in transit, and secret management. They evaluate defense-in-depth strategies and flag high-risk changes that lack validation plans.