skills.rest
OM-bit-hub
OM-bit-hubCOMMUNITY
Explore all skills by this author →
GitHub

arch-review

Audit architecture designs for scalability, coupling, and single points of failure.

Updated Aug 23, 2026
Search Tags:#architecture#scalability#system-design#architecture-review#fault-tolerance#operational-readiness
One-click install
npx skills add https://github.com/OM-bit-hub/daily_tracker --skill arch-review-om-bit-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-review
Source: https://github.com/OM-bit-hub/daily_tracker/tree/main/.agents/skills/lead-engineer/arch-review
Command: npx skills add https://github.com/OM-bit-hub/daily_tracker --skill arch-review-om-bit-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits architecture decisions for scalability, coupling, single points of failure, and maintainability before committing to a design, during system design reviews, or when refactoring critical subsystems.

Core Features & Use Cases

  • Topology mapping and risk scoring across subsystems
  • Coupling, scalability, and fault-tolerance evaluations with actionable recommendations
  • Use Cases: before major design decisions, during design reviews, or after outages to surface architectural concerns and trade-offs

Quick Start

Provide the architecture design you want reviewed and let arch-review generate a prioritized findings report.

Frequently Asked Questions about arch-review

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

FAQPage Schema
How do I review an architecture design for scalability bottlenecks and single points of failure?▼

An architecture review identifies scalability bottlenecks, coupling risks, and single points of failure by auditing system topology, data flows, and failure modes against criteria for modularity and fault tolerance.

What is the best way to assess fault tolerance and operational readiness during a system design review?▼

The best way to assess fault tolerance and operational readiness during a system design review is to evaluate failure modes using structured checklists that enforce criteria for modularity, data integrity, and scalability.

When do I need to run an architecture review for a system refactor or RFC discussion?▼

You need to run an architecture review during RFC discussions, before major design decisions, or after outages to surface architectural concerns, evaluate topology risks, and assess operational readiness for critical subsystem refactors.

Can I use a structured checklist to identify coupling risks and data integrity issues before coding?▼

Yes, you can use a structured checklist to identify coupling risks and data integrity issues before coding by auditing your architecture decisions and generating a prioritized findings report with actionable recommendations.

What are the limitations of relying on an architecture review for system design?▼

The limitation of an architecture review for system design is that it assesses theoretical topology, data flows, and failure modes before implementation, meaning it cannot validate actual runtime performance or real-world operational behavior.

Related Skills

Explore More Software Engineering Skills→
ggazzoggazzo

reversa-designer

Automate system migration design and architecture planning with Reversa framework.

Community
Advanced
shafibabarshafibabar
1

data-pipeline-design

Design data pipeline topologies with processing modes, transformation strategies, and fault-tolerance mechanisms.

Community
Advanced
mofa-orgmofa-org
11

mofa-agent-topology

Generate topology diagrams from Gateway RouteRegistry or coordination graph layouts.

Official
Advanced
Design-System-ETDesign-System-ET

chaos-engineer

Design and execute chaos experiments to validate system resilience in distributed environments.

Official
Advanced