architecture-designer

Name: architecture-designer
Availability: InStock
Author: gabi-agent

Design scalable software architectures and produce ADRs from requirements.

Updated Feb 26, 2026

Search Tags:#architecture #scalability #adr #design-patterns #system-design #architecture-review #adr-template

Ready to run

npx skills add https://github.com/gabi-agent/openretro --skill architecture-designer-gabi-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/gabi-agent/openretro/tree/main/skills/architecture-designer
Command: npx skills add https://github.com/gabi-agent/openretro --skill architecture-designer-gabi-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Architecture Designer helps teams design robust, scalable software architectures and provides a disciplined approach to architectural decisions, reviews, and ADR documentation.

Core Features & Use Cases

Understand requirements and constraints to shape architectural decisions.
Identify appropriate architectural patterns, evaluate trade-offs, and select technologies.
Create high-level architectures and ADRs, then review decisions with stakeholders.
Plan for non-functional requirements and operational considerations (scalability, reliability, security, maintainability).

Quick Start

Provide a complete system design for a scalable service, including ADRs and a rationale for the chosen architectural patterns.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema

How do I design scalable software architecture for distributed systems?▼

To design scalable software architecture, analyze system requirements and constraints to identify appropriate design patterns, evaluate technology trade-offs, and outline non-functional requirements. This delivers a clear, decision-ready architecture for distributed systems.

What is an ADR template and when do I need it for system design?▼

An ADR (Architecture Decision Record) template documents architectural decisions, capturing context, decisions, and consequences. You need ADRs during system design to provide a disciplined rationale for chosen patterns and technologies to stakeholders.

How do I select the right design patterns for an architecture review?▼

Selecting design patterns for an architecture review requires evaluating trade-offs against your non-functional requirements and operational constraints. Identify appropriate architectural patterns by analyzing scalability, reliability, and maintainability needs to ensure robust system design.

What's the best way to document non-functional requirements for scalability planning?▼

The best way to document non-functional requirements for scalability planning is to outline operational considerations like reliability, security, and maintainability alongside your high-level architecture. This ensures distributed systems meet performance targets while maintaining structural integrity.

Does this approach work for evaluating trade-offs in technology selection?▼

Yes, evaluating technology trade-offs works by analyzing your specific requirements and constraints to select appropriate architectural patterns. This disciplined approach ensures technology selection aligns with non-functional requirements and operational considerations for robust systems.