architecture-review

Review architecture documents for risks, bottlenecks, and improvement opportunities.

1|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill architecture-review-acidicsoil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill architecture-review-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Peer-review architecture documents to identify risks, bottlenecks, and opportunities for improvement, enabling quality assurance and informed decisions.

Core Features & Use Cases

  • Structured evaluation across scalability, security, performance, maintainability, and technology fit.
  • Actionable recommendations with prioritized plans to guide architecture improvements.
  • Scenario-based reviews for proposals, design docs, and architecture diagrams across teams.

Quick Start

Provide an architecture document to initiate a guided peer-review with prioritized findings and recommendations.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I review architecture documents for scalability and security risks?

Review architecture documents by peer-evaluating them against comprehensive criteria including scalability, security, performance, maintainability, and technology fit to identify bottlenecks and prioritize actionable improvement recommendations.

What is the best way to evaluate design docs for performance bottlenecks?

Evaluating design docs for performance bottlenecks involves a structured peer-review assessing scalability, maintainability, and technology fit, ultimately producing prioritized, actionable recommendations to guide architecture improvements.

Can I use an architecture review for team proposals and diagrams?

Yes, scenario-based architecture reviews can be applied to team proposals, design documents, and architecture diagrams to identify risks, bottlenecks, and opportunities for informed decision-making across projects.

How do I get prioritized recommendations from an architecture proposal?

To get prioritized recommendations from an architecture proposal, provide the document to initiate a guided peer-review that evaluates risks across multiple criteria and outputs an actionable improvement plan.

What criteria are evaluated during an architecture risk assessment?

An architecture risk assessment evaluates documents against a comprehensive set of criteria: scalability, security, performance, maintainability, technology fit, and actionable recommendations to ensure quality assurance.

When do I need a peer-review for my architecture decisions?

You need a peer-review for architecture decisions when you want to identify potential risks, bottlenecks, and improvement opportunities across teams and projects to ensure quality assurance and informed decisions.