architecture

Analyzes requirements and trade-offs to document architectural decisions.

Updated May 3, 2026

Search Tags:#architecture #system design #requirements analysis #ADR #trade-offs #decision-making

Ready to run

npx skills add https://github.com/Durannd/skills --skill architecture-durannd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Durannd/skills/tree/main/skills/architecture
Command: npx skills add https://github.com/Durannd/skills --skill architecture-durannd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework to analyze, evaluate, and document architectural decisions, ensuring systematic and well-informed system design.

Core Features & Use Cases

Requirements Analysis: Guides gathering and analyzing system requirements and constraints.
Trade-off Evaluation: Supports comparing different architectural options with pros and cons.
ADR Documentation: Facilitates recording and revisiting decisions to maintain clarity and accountability.
Use Case: When designing a new software system, use this Skill to analyze scalability, technology choices, and document each decision with trade-offs for future reference.

Quick Start

Use the architecture skill to evaluate trade-offs in choosing between microservices and monolith architecture for a new project.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document system design decisions and evaluate architectural trade-offs?▼

To document system design decisions, you analyze project constraints, evaluate architectural trade-offs like microservices versus monoliths, and record the justification in an Architecture Decision Record to ensure traceability and accountability.

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

An Architecture Decision Record (ADR) is a document capturing software design choices, their trade-offs, and constraints. You need it when making significant technology selections or deployment pattern choices to maintain clarity for future reference.

How to analyze requirements and choose between microservices and monolith architecture?▼

Analyze requirements by gathering system constraints and evaluating scalability needs, then compare microservices and monolith options by documenting their specific pros and cons to justify your architectural selection.

Can I use this framework for deployment strategy decisions and technology selection?▼

Yes, you can use this framework for deployment strategy decisions and technology selection. It facilitates systematic decision-making by aligning your technology choices and deployment patterns with project constraints.

What are the limitations of relying on systematic architecture decision-making frameworks?▼

Systematic architecture decision-making frameworks require thorough requirements analysis and trade-off evaluation upfront. Limitations include the time investment needed to document decisions and the necessity of having clearly defined project constraints before evaluating options.

Why does evaluating architectural trade-offs help with system design accountability?▼

Evaluating architectural trade-offs helps with system design accountability by ensuring every technology and pattern selection is well-justified, traceable to project constraints, and documented for future revisiting and clarity.