arch-review

Audit system architectures for scalability bottlenecks, coupling, SPOFs, and maintainability gaps.

13|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill arch-review-heaptracetechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-review
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/lead-engineer/arch-review
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill arch-review-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers evaluate architecture decisions to identify scalability bottlenecks, tight coupling, single points of failure, and maintainability gaps, so teams can design more resilient systems.

Core Features & Use Cases

  • Formalize architecture reviews before major design changes or refactors.
  • Identify SPOFs, coupling issues, data-flow problems, and non-functional risks across subsystems.
  • Provide structured recommendations and guardrails to guide architecture decisions during design reviews and critical rewrites.

Quick Start

Execute a structured architecture review on a new or existing subsystem to surface risks and recommended mitigations.

Frequently Asked Questions about arch-review

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

FAQPage Schema
How do I conduct an architecture review to identify scalability bottlenecks?

An architecture review evaluates system topology and data flow to identify scalability bottlenecks, tight coupling, and single points of failure. It provides structured risk assessments and actionable mitigations to guide design decisions during major refactors or subsystem changes.

What is the best way to assess single points of failure and coupling in system design?

Assessing single points of failure and coupling in system design involves mapping topology and data flow to expose structural risks. A formal architecture audit identifies these maintainability gaps and provides recommended guardrails to improve system resilience.

When do I need a formal architecture audit before refactoring a subsystem?

You need a formal architecture audit before major refactors, critical rewrites, or subsystem evaluations. It surfaces non-functional risks, SPOFs, and data-flow constraints, ensuring teams address maintainability gaps and scalability limits before committing to design changes.

Can I evaluate non-functional requirements and data flow across existing subsystems?

You can evaluate non-functional requirements and data flow across existing subsystems through a structured architecture review. It maps system topology to detect coupling issues and scalability limits, delivering staff-level risk assessments with actionable mitigations.

How does topology mapping work during a system design review?

Topology mapping during a system design review traces component interactions and data flow to pinpoint single points of failure and tight coupling. It forms the basis for a risk assessment, yielding structured recommendations and guardrails for architecture improvements.