architect-review

Assesses architectural decisions and identifies risks in complex software systems.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/raksok/netherica --skill architect-review-raksok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-review
Source: https://github.com/raksok/netherica/tree/main/.agents/skills/architect-review
Command: npx skills add https://github.com/raksok/netherica --skill architect-review-raksok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams ensure architectural integrity, evaluate major design changes, and guide strategic technical decisions.

Core Features & Use Cases

  • Architectural reviews: assess decisions, identify risks, and propose improvements with trade-offs.
  • Documentation: produce Architecture Decision Records (ADRs) and rationale for governance.
  • Guidance for complex systems: ensure scalability, resilience, and maintainability across distributed components.

Quick Start

Provide a high-level architectural review of the current system and generate an ADR with recommended changes and 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 software architecture for scalability and identify risks during a system redesign?

Architecture Decision Records (ADRs) document architectural decisions and rationale for governance. They are produced during an architectural review to capture trade-offs, recommended changes, and identified risks, ensuring maintainability and strategic alignment across complex software systems.

How do I evaluate microservices and clean architecture trade-offs across bounded contexts?

Domain-Driven Design (DDD) is evaluated during architectural reviews to ensure architectural integrity across complex systems. It helps define bounded contexts, assess distributed components, and guide major design changes, ensuring scalability and maintainability throughout the system redesign.

What is the best way to document architectural decisions and rationale for governance?

The best way to document architectural decisions is by generating Architecture Decision Records (ADRs). ADRs capture the rationale, trade-offs, and risk analysis for major design changes, providing a structured evaluation that guides governance and ensures long-term maintainability.

When do I need an architectural review for distributed systems and cloud-native concerns?

You need an architectural review when systems undergo major redesign or scale-up involving distributed systems and cloud-native concerns. It evaluates architectural integrity, identifies risks in complex software, and proposes improvements with trade-offs for resilience and scalability.