architect-review

Review complex software system architectures for scalability, resilience, and maintainability.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/stevenengland/sten-agent-skills --skill architect-review-stevenengland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-review
Source: https://github.com/stevenengland/sten-agent-skills/tree/main/skills/architect-review
Command: npx skills add https://github.com/stevenengland/sten-agent-skills --skill architect-review-stevenengland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides expert architectural guidance to ensure system designs meet scalability, maintainability, and resilience requirements across complex distributed systems.

Core Features & Use Cases

  • Architectural reviews for complex systems to assess decisions and align with standards.
  • Evaluate scalability, resilience, and maintainability implications across services, data flows, and deployment patterns.
  • Document decisions, risks, and recommended improvements with clear tradeoffs and validation.

Quick Start

Provide system context, goals, constraints, and current architecture details to receive an architectural review.

Frequently Asked Questions about architect-review

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

FAQPage Schema
How do I review software architecture for scalability and maintainability in distributed systems?

To review software architecture for scalability and maintainability, provide system context, goals, constraints, and current architecture details to receive a rigorous assessment of decisions, risks, and recommended improvements across distributed systems.

What is included in an architectural review for microservices and cloud-native transitions?

An architectural review for microservices and cloud-native transitions includes evaluating scalability, resilience, and maintainability implications, documenting decisions, identifying risks, and proposing actionable improvements with clear tradeoffs and validation plans.

When do I need an architectural review for a system redesign or technology evaluation?

You need an architectural review during system redesigns, major architectural changes, technology evaluations, and cloud-native transitions to ensure complex software designs meet scalability, resilience, and maintainability requirements across data pipelines and integration layers.

Can I evaluate clean architecture and DDD patterns for my current software system?

You can evaluate clean architecture and DDD patterns by submitting your current architecture details and constraints for a rigorous review that aligns system decisions with standards and identifies actionable improvements across services and data flows.

Does this approach support documenting architectural decisions and tradeoffs for complex systems?

This approach supports documenting architectural decisions by providing rigorous reviews that capture decisions, risks, and recommended improvements with clear tradeoffs and validation plans tailored to complex software systems and distributed environments.

What are the limitations of using automated architectural reviews for major system changes?

Automated architectural reviews depend on the accuracy of provided system context, goals, and constraints, meaning incomplete input about complex distributed systems or data pipelines may limit the depth of risk identification and proposed tradeoffs.