skills.rest
alessioroberto82
alessioroberto82COMMUNITY
Explore all skills by this author →
GitHub

arch

Design system architecture and document decisions with ADRs.

1|Updated Feb 19, 2026
Search Tags:#architecture#software engineering#scalability#system design#ADR#technology stack
One-click install
npx skills add https://github.com/alessioroberto82/claude-plugin-bmad --skill arch-alessioroberto82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch
Source: https://github.com/alessioroberto82/claude-plugin-bmad/tree/main/plugin/skills/arch
Command: npx skills add https://github.com/alessioroberto82/claude-plugin-bmad --skill arch-alessioroberto82

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the complexity of designing robust, maintainable, and scalable software architectures, ensuring technical decisions are well-reasoned and documented.

Core Features & Use Cases

  • System Design: Creates high-level component diagrams and defines module interactions.
  • Technology Evaluation: Assesses and selects appropriate technology stacks with justifications.
  • ADR Generation: Documents significant technical decisions using the Architecture Decision Record format.
  • Use Case: When starting a new project, use this Skill to define the core services, database choices, and API contracts, ensuring a solid foundation for development.

Quick Start

Use the arch skill to design the architecture for a new microservice based on the provided requirements.

Frequently Asked Questions about arch

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

FAQPage Schema
How do I design scalable software architecture for a new project?▼

Design scalable software architecture by defining high-level component diagrams and module interactions. Evaluate technology trade-offs to create a robust, maintainable foundation for new development.

What is an Architecture Decision Record and when do I need it?▼

An Architecture Decision Record (ADR) documents significant technical decisions and their justifications. You need ADRs when selecting a technology stack or defining system design to ensure choices are well-reasoned and traceable.

How do I evaluate technology stack trade-offs for system design?▼

Evaluate technology stack trade-offs by assessing and selecting appropriate technologies based on specific justifications. This ensures the chosen stack aligns with scalability requirements and maintainability goals.

Can I use this approach to refactor existing software systems?▼

Yes, you can refactor existing software systems by analyzing current requirements and exploring the codebase. This allows you to redefine the system architecture and document updates using ADRs.

What is the best way to document technical decisions for microservices?▼

The best way to document technical decisions for microservices is using the Architecture Decision Record (ADR) format, which captures the context, decision, and consequences of each architectural choice.

Related Skills

Explore More Software Engineering Skills→
hajrasarwar11hajrasarwar11

design-exploration

Analyze component context and constraints to produce a structured design brief.

Community
Advanced
OreStudioOreStudio
25

system-architect

Analyze system architecture and generate incremental migration plans from PlantUML diagrams.

Official
Advanced
tunneleventunneleven

c4flow:infra

Generate Infrastructure as Code configurations from a tech-stack.md file.

Community
Basic
paulinghampaulingham
1

voice-scaffold

Scaffold voice-skill projects across Alexa, Google Actions, and Twilio IVR.

Community
Intermediate