skills.rest
Jet-labs
Jet-labsOFFICIAL
Explore all skills by this author →
GitHub

architect-review

Identify architectural gaps and risks in system designs and document ADRs.

Updated Feb 10, 2026
Search Tags:#architecture#microservices#ddd#review#clean-architecture#system-design
One-click install
npx skills add https://github.com/Jet-labs/jet-pg-admin --skill architect-review-jet-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-review
Source: https://github.com/Jet-labs/jet-pg-admin/tree/main/.agent/skills/architect-review
Command: npx skills add https://github.com/Jet-labs/jet-pg-admin --skill architect-review-jet-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams evaluate system architecture to ensure scalability, resilience, and maintainability by applying modern architecture patterns such as clean architecture, microservices, and domain-driven design.

Core Features & Use Cases

  • Gather system context, goals, and constraints to establish a baseline for architectural review.
  • Evaluate design decisions for alignment with established patterns (clean architecture, DDD, event-driven design) and identify risks and trade-offs.
  • Propose concrete improvements with actionable next steps and document decisions and rationales in Architecture Decision Records (ADRs) for traceability.
  • Provide guidance to stakeholders across teams to align on architecture strategy and long-term maintainability.

Quick Start

Provide the system design for review and request an architectural assessment with risks, tradeoffs, and recommended improvements.

Frequently Asked Questions about architect-review

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

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

To review system architecture for scalability and resilience, evaluate design decisions against established patterns like clean architecture and DDD to identify gaps, risks, and trade-offs. This process establishes a baseline using your system's goals and constraints.

What is the best way to evaluate microservices and domain-driven design boundaries?▼

Evaluating microservices and domain-driven design boundaries involves assessing your integration limits and data streaming structures against governance-aligned recommendations. This identifies architectural gaps and provides actionable improvements for distributed systems.

How do I document architectural decisions and rationales for traceability?▼

Document architectural decisions and rationales by recording them in Architecture Decision Records (ADRs). ADRs capture the context, evaluated decisions, proposed improvements, and trade-offs to ensure long-term traceability and stakeholder alignment.

Can I use an architecture review for large-scale distributed systems and data streaming?▼

Yes, you can apply architectural reviews to large-scale distributed systems and data streaming infrastructures. The review process evaluates integration boundaries and evaluates decisions to ensure maintainability and governance alignment.

What are the limitations of clean architecture for microservices?▼

Limitations of clean architecture in microservices include potential trade-offs in integration boundaries and communication overhead. Evaluating these risks against domain-driven design patterns helps propose concrete improvements while maintaining system governance.

Related Skills

Explore More Software Engineering Skills→
HechaoYannetHechaoYannet

create-architecture

Generate a master architecture document from GDDs, ADRs, and governance constraints.

Community
Advanced
686f6c61686f6c61
105

write-adr

Generate Architecture Decision Records documenting context, alternatives, decision, and consequences.

Community
Intermediate
89jobrien89jobrien
4

golang-enterprise-patterns

Design Go applications with clean or hexagonal architecture and Domain-Driven Design.

Community
Advanced
EstomEstom

architecture-designer

Design system architectures and document key architectural decisions with ADRs.

Community
Advanced