architecture-review

Inventory architectural decisions and generate actionable recommendations with Architecture Decision Records.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ashtonian/llm-init --skill architecture-review-ashtonian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/ashtonian/llm-init/tree/main/templates/.claude/skills/architecture-review
Command: npx skills add https://github.com/ashtonian/llm-init --skill architecture-review-ashtonian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture reviews help teams surface flawed or suboptimal design decisions early, reducing risk and rework.

Core Features & Use Cases

  • Inventory architectural decisions across codebases and specs
  • Assess fitness, tradeoffs, scalability, and maintainability of designs
  • Generate actionable recommendations and ADRs to document decisions

Quick Start

Run a comprehensive architecture review on the current codebase to surface decisions, risks, and improvement opportunities.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I conduct an architecture review to surface design risks in my codebase?

An architecture review inventories existing architectural decisions across your codebase to evaluate tradeoffs, fitness, and scalability. It identifies maintainability issues and risks early, providing actionable recommendations to reduce rework.

How do I generate Architecture Decision Records for my system design?

You can generate Architecture Decision Records (ADRs) by assessing your system design and documenting the evaluated tradeoffs and outcomes. This formalizes architectural decisions for stakeholders and ensures alignment across the team.

Can I assess the scalability and fitness of a specific feature area's architecture?

Yes, you can evaluate a specific feature area by applying phased methods to assess its architectural fitness and scalability. This surfaces targeted tradeoffs and maintainability issues within that isolated scope.

What is the best way to inventory architectural decisions across existing specs?

Inventorying architectural decisions involves systematically identifying and cataloging design choices across codebases and specifications. This process highlights existing tradeoffs and surfaces suboptimal patterns for stakeholder review.

When do I need a formal architecture review for my system design?

You need a formal architecture review when you want to surface flawed or suboptimal design decisions early in the lifecycle. This reduces risk and rework by evaluating maintainability and fitness before issues scale.

Does the architecture review process output actionable recommendations for stakeholders?

Yes, the architecture review process outputs actionable recommendations and documented findings specifically tailored for stakeholders. It evaluates design tradeoffs and generates ADRs to formalize the outcomes.