architecture-analysis

Name: architecture-analysis
Availability: InStock
Author: front-depiction

Analyze architectural dependencies and impact across multi-service systems.

Updated Aug 23, 2026

Search Tags:#architecture #dependencies #analyze #root-cause #blast-radius #domain-discovery

Ready to run

npx skills add https://github.com/front-depiction/claude-setup --skill architecture-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-analysis
Source: https://github.com/front-depiction/claude-setup/tree/main/skills/architecture-analysis
Command: npx skills add https://github.com/front-depiction/claude-setup --skill architecture-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides in-depth architectural dependency analysis and impact assessment to understand how services are connected, how changes propagate, and where risk concentrates.

Core Features & Use Cases

Full graph dependency analysis with the architecture CLI (analyze, blast-radius, ancestors, common-ancestors, metrics, domains, hot-services).
Progressive disclosure outputs (XML/structured data) for automation and reporting.
Guidance for planning safe changes, domain boundaries, and capacity planning across large service graphs.

Quick Start

Run a full analysis: use ./.claude/bin/architecture analyze
View metrics: ./.claude/bin/architecture analyze --metrics
Inspect domains and hot services: ./.claude/bin/architecture domains
Check blast radius for a service: ./.claude/bin/architecture blast-radius ServiceName
Explore upstream dependencies: ./.claude/bin/architecture ancestors ServiceName

Frequently Asked Questions about architecture-analysis

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

FAQPage Schema

How do I analyze service dependencies and evaluate blast radius in a multi-service architecture?▼

Dependency analysis and blast-radius evaluation are performed by executing the architecture CLI to map service connections and assess how changes propagate across multi-service systems. The tool generates structured data for impact assessment.

What is the best way to discover domain boundaries and identify hot services in a large service graph?▼

Domain discovery and hot-service identification are achieved by running the architecture CLI domains command. It inspects large service graphs to reveal domain boundaries and highlight where risk and dependency concentrations accumulate.

Can I trace root-cause issues and upstream dependencies for a specific service?▼

Root-cause analysis and upstream dependency tracing are supported through the architecture CLI ancestors command, which explores the service graph to identify the origin of failures and their ancestral dependency chains.

Does this architectural dependency analysis require a specific project layout or environment?▼

Architectural dependency analysis requires a TypeScript project layout under the ./src directory by default. It also expects the architecture CLI to be accessible at .claude/bin/architecture to execute dependency and impact assessment commands.

How do I run a full architectural dependency analysis and view service metrics?▼

Run a full dependency analysis using the .claude/bin/architecture analyze command. To view service metrics specifically, append the --metrics flag to generate structured data for capacity planning and stability checks.