architecture-review

Review system architecture documents for tradeoffs and design issues.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/shex1627/shudaizi-mcp --skill architecture-review-shex1627
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/shex1627/shudaizi-mcp/tree/main/skills/architecture-review
Command: npx skills add https://github.com/shex1627/shudaizi-mcp --skill architecture-review-shex1627

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring robust, scalable, and maintainable software architectures by providing a systematic review process and access to established architectural principles.

Core Features & Use Cases

  • Systematic Review: Guides users through a phased assessment of system design against best practices.
  • Tradeoff Analysis: Helps identify and articulate the pros and cons of architectural decisions.
  • Deep-Dive References: Provides access to foundational knowledge from key software architecture books for in-depth understanding.
  • Use Case: When designing a new microservices-based system, use this Skill to review the proposed service boundaries, communication patterns, and data consistency strategies against established principles.

Quick Start

Review the provided system architecture document for potential issues and tradeoffs.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I conduct a systematic architecture review for a microservices system design?

A systematic architecture review assesses your microservices system design against established software engineering principles using a phased approach. It evaluates service boundaries, communication patterns, and data consistency strategies to ensure robustness and maintainability.

When do I need to analyze architectural tradeoffs and complexity justification?

You need architectural tradeoff analysis when evaluating ADRs or making system design decisions. It helps articulate pros and cons while justifying complexity, managing dependencies, and ensuring resilience according to established software engineering principles.

What is the best way to evaluate architectural decision records against best practices?

The best way to evaluate ADRs is through a systematic review process that checks architectural decisions against established best practices. This process analyzes tradeoffs, dependency management, and complexity justification using cited foundational references.

Can I use this approach to review communication patterns and data consistency strategies?

Yes, you can review communication patterns and data consistency strategies by guiding a phased assessment of your proposed system architecture. This review checks your microservices design against established principles to identify potential issues and tradeoffs.

What are the limitations of automated system design reviews for microservices?

Automated system design reviews are limited by their reliance on provided architecture documents and established principles. They cannot discover undocumented dependencies or runtime behaviors, focusing strictly on reviewing stated design logic and analyzing architectural tradeoffs.