skills.rest
Movchanets
MovchanetsCOMMUNITY
Explore all skills by this author →
GitHub

architect-review

Reviews distributed architecture decisions for scalability, maintainability, resilience, and security risks.

Updated May 5, 2026
Search Tags:#architecture#microservices#ddd#clean architecture#resilience#distributed systems#cqrs
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill architect-review-movchanets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-review
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/architect-review
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill architect-review-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams evaluate complex software architecture decisions before they create scalability, maintainability, security, or reliability problems.

Core Features & Use Cases

  • Architecture Review: Assess service boundaries, dependency direction, and design consistency across distributed systems.
  • Quality Tradeoff Analysis: Weigh scalability, resilience, testability, and operational complexity when designs change.
  • Guidance for Modern Patterns: Apply clean architecture, DDD, CQRS, event-driven design, and cloud-native principles to real projects.
  • Use Case: A team planning a new microservice or major refactor can use this Skill to identify risks, recommend improvements, and document the architectural rationale.

Quick Start

Ask this skill to review your system design, identify architectural risks, and recommend concrete improvements with tradeoffs.

Frequently Asked Questions about architect-review

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

FAQPage Schema
How do I review microservices architecture for scalability and resilience risks?▼

Assess service boundaries, dependency direction, and design consistency across your distributed system to identify scalability, maintainability, and resilience risks before they impact production.

What is the best way to apply DDD and clean architecture to an event-driven system?▼

Apply DDD and clean architecture by aligning bounded contexts, evaluating asynchronous messaging patterns, and ensuring your event-driven design maintains clear dependency direction and testability.

How do you analyze quality tradeoffs when refactoring distributed systems?▼

Analyze quality tradeoffs by weighing scalability, resilience, testability, and operational complexity against your specific architectural changes to document the rationale and recommend concrete improvements.

Can I use this approach to evaluate CQRS patterns and API gateway decisions?▼

Yes, you can evaluate CQRS patterns and API gateway decisions by checking their alignment with cloud-native principles, asynchronous messaging, and documented validation plans within your architecture.

When should I not use microservices for a major system refactor?▼

You should reconsider microservices if the architectural review reveals excessive operational complexity, unclear bounded contexts, or tradeoffs where maintainability and testability costs outweigh scalability benefits.

Related Skills

Explore More Software Engineering Skills→
DevXojeDevXoje

clean-architecture

Validate dependency rules and layer boundaries for Clean Architecture compliance.

Community
Intermediate
AbsolutSystemsAbsolutSystems
1

tech-lead-advisor

Evaluates architectural proposals for scalability, maintainability, security, and delivery fit with explicit tradeoffs.

Official
Advanced
stephanjstephanj
9

chaos-engineer

Design and execute controlled chaos engineering experiments for Kubernetes clusters.

Community
Advanced
AsiaOstrichAsiaOstrich
70

discover

Assess project health, architecture, and risks in existing codebases.

Community
Intermediate