architecture-advisor

Evaluate architectural decisions and generate Architecture Decision Records.

2|1|Updated Feb 27, 2026

Search Tags:#design #architecture #refactoring #system design #technical debt #ADR

Ready to run

npx skills add https://github.com/Kaakati/sdh-claude-skills --skill architecture-advisor-kaakati

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-advisor
Source: https://github.com/Kaakati/sdh-claude-skills/tree/main/.claude/skills/architecture-advisor
Command: npx skills add https://github.com/Kaakati/sdh-claude-skills --skill architecture-advisor-kaakati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert architectural guidance, helping to design robust systems, evaluate technical decisions, and document them effectively through Architecture Decision Records (ADRs).

Core Features & Use Cases

System Design: Get recommendations for designing new system components or services.
Technology Evaluation: Assess trade-offs between different technologies or approaches.
ADR Generation: Produce formal Architecture Decision Records for key architectural choices.
Technical Debt Assessment: Identify and plan remediation for existing technical debt.

Quick Start

Use the architecture-advisor skill to design a scalable backend for a new e-commerce platform.

Frequently Asked Questions about architecture-advisor

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

FAQPage Schema

How do I write an Architecture Decision Record for system design choices?▼

An Architecture Decision Record (ADR) documents key architectural choices and their trade-offs. You generate formal ADRs by evaluating technical decisions, assessing technology options, and capturing the context, decision, and consequences for system design.

What is the best way to assess technical debt before refactoring?▼

Assessing technical debt involves evaluating existing architectural decisions and identifying areas needing remediation. You analyze system components to pinpoint structural issues, plan refactoring strategies, and document the required quality attribute improvements.

How do I evaluate technology trade-offs when designing new system components?▼

Evaluating technology trade-offs requires comparing different approaches against your system's quality attributes. You assess architectural decisions to determine the best fit for designing new system components, ensuring the selected technology aligns with your scalability requirements.

Can I use this for system architecture design at a large scale?▼

Yes, system architecture design applies to large-scale scenarios requiring strategic technical guidance. It supports designing scalable backend services, analyzing quality attributes, and producing formal documentation for complex system components.

When do I need formal architectural documentation for refactoring planning?▼

You need formal architectural documentation when planning refactoring to ensure structural changes align with strategic goals. Generating ADRs during refactoring planning captures the technical debt remediation context and prevents unintended architectural degradation.

Does system design require analyzing quality attributes?▼

Yes, system design requires quality attribute analysis to ensure robust architecture. Evaluating architectural decisions involves assessing trade-offs across quality attributes like scalability and performance to produce effective technical guidance and formal documentation.