architecture

Analyze architectural trade-offs and document decisions with ADR templates.

Updated Mar 7, 2026

Search Tags:#architecture #decision making #system design #adr #patterns #trade-offs

Ready to run

npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill architecture-geargrindadmin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Geargrindadmin/gg-agentic-harness/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill architecture-geargrindadmin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for making sound architectural decisions, analyzing trade-offs, and documenting them effectively using Architecture Decision Records (ADRs).

Core Features & Use Cases

Requirements Analysis: Guides the process of understanding project needs and constraints.
Trade-off Evaluation: Provides methods for comparing different architectural options.
ADR Documentation: Offers templates and guidance for creating clear, concise ADRs.
Use Case: When designing a new microservice, use this Skill to analyze different database choices, API patterns, and communication protocols, documenting the final decision and its rationale.

Quick Start

Use the architecture skill to analyze trade-offs for a new microservice's data storage.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document architectural decisions for a new microservice?▼

You can document architectural decisions by using Architecture Decision Record (ADR) templates to capture design choices, trade-offs, and rationale. This ensures systematic context discovery and clear communication of system design choices.

What is the best way to analyze trade-offs in system design?▼

Analyzing trade-offs in system design requires structured frameworks to compare architectural options like database choices and API patterns. This provides methods for evaluating constraints and selecting optimal patterns for your software.

How do I write an Architecture Decision Record for API patterns?▼

Writing an Architecture Decision Record for API patterns involves using trade-off analysis templates to document the selected pattern and its rationale. This captures the context and systematic design choices for your software systems.

Can I use this framework for requirements analysis before choosing database patterns?▼

Yes, this framework guides requirements analysis to understand project needs and constraints before selecting database patterns. It supports context discovery and systematic evaluation of architectural options for your software system.

When do I need an architectural decision-making framework?▼

You need an architectural decision-making framework when designing new software systems and facing complex choices like communication protocols or data storage. It facilitates systematic requirements analysis and rationale capture for trade-off evaluation.